<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 17 Nov 2026 14:15:44 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-98811 — net/sched: cls_api: reclaim an empty proto on the error path</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-98811</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/sched: cls_api: reclaim an empty proto on the error path&lt;/p&gt;
&lt;p&gt;Two racing tc filter add requests on the same chain/prio of an
unlocked classifier both run change() on the shared proto and both
can fail: the winner&amp;#39;s tcf_chain_tp_delete_empty() attempt gives up
because the loser&amp;#39;s handle is still in the idr, and the loser&amp;#39;s
error path drops only its own reference without a second reclamation
attempt. The empty proto stays linked in the chain, holding the
chain reference, a block reference and the classifier module
reference until the chain or block is torn down.&lt;/p&gt;
&lt;p&gt;Reclaim the proto on the error path of any failed request that holds
a proto reference. The reclamation is emptiness-gated:
tcf_chain_tp_delete_empty() unlinks the proto only when
delete_empty() admits it is empty, so a live shared proto is never
unlinked. A proto the request created is reclaimed unconditionally -
it is the only owner, so marking it for deletion is safe even without
a delete_empty callback. Classifiers without one (the check marks the
proto unconditionally) are rtnl-serialized, so the raced window this
guard closes cannot arise for them.&lt;/p&gt;
&lt;p&gt;This is a follow-up to commit d4e359b3608a (&amp;#34;net/sched: cls_api: fix
teardown of an adopted proto on insert-race loss&amp;#34;), which stopped the
loser of the insert race from unlinking the winner&amp;#39;s live proto but
left the empty-proto residual in place.&lt;/p&gt;
&lt;p&gt;Conditions to recreate:
- CONFIG_NET_CLS_FLOWER=y; v…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/sched: cls_api: reclaim an empty proto on the error path&lt;/p&gt;
&lt;p&gt;Two racing tc filter add requests on the same chain/prio of an
unlocked classifier both run change() on the shared proto and both
can fail: the winner&amp;#39;s tcf_chain_tp_delete_empty() attempt gives up
because the loser&amp;#39;s handle is still in the idr, and the loser&amp;#39;s
error path drops only its own reference without a second reclamation
attempt. The empty proto stays linked in the chain, holding the
chain reference, a block reference and the classifier module
reference until the chain or block is torn down.&lt;/p&gt;
&lt;p&gt;Reclaim the proto on the error path of any failed request that holds
a proto reference. The reclamation is emptiness-gated:
tcf_chain_tp_delete_empty() unlinks the proto only when
delete_empty() admits it is empty, so a live shared proto is never
unlinked. A proto the request created is reclaimed unconditionally -
it is the only owner, so marking it for deletion is safe even without
a delete_empty callback. Classifiers without one (the check marks the
proto unconditionally) are rtnl-serialized, so the raced window this
guard closes cannot arise for them.&lt;/p&gt;
&lt;p&gt;This is a follow-up to commit d4e359b3608a (&amp;#34;net/sched: cls_api: fix
teardown of an adopted proto on insert-race loss&amp;#34;), which stopped the
loser of the insert race from unlinking the winner&amp;#39;s live proto but
left the empty-proto residual in place.&lt;/p&gt;
&lt;p&gt;Conditions to recreate:
- CONFIG_NET_CLS_FLOWER=y; v…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-98811</guid>
    </item>
    <item>
      <title>USN-9018-1 — linux, linux-aws, linux-gcp, linux-ibm, linux-oem-7.0, linux-oracle vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-9018-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oem-7.0, Ubuntu:26.04:LTS: linux-oracle&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - Network file systems library;
  - Stream parser;
  - ARM64 architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Android drivers;
  - Bluetooth drivers;
  - TPM device driver;
  - DPLL subsystem;
  - EDAC drivers;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - IIO subsystem;
  - IIO ADC drivers;
  - InfiniBand drivers;
  - Input Device (Miscellaneous) drivers;
  - Multiple devices driver;
  - MemoryStick subsystem;
  - MMC subsystem;
  - MTD block device drivers;
  - Network drivers;
  - Ethernet bonding driver;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - Ethernet team driver;
  - MediaTek network drivers;
  - NVME drivers;
  - Device tree and open firmware driver;
  - Power sequencing drivers;
  - Voltage and Current Regulator drivers;
  - Real Time Clock drivers;
  - SCSI subsystem;
  - Greybus lights staging drivers;
  - Trusted Execution Environment drivers;
  - Thunderbolt and USB4 drivers;
  - TTY drivers;
  - Cadence USB3 driver;
  - USB Device Class drivers;
  - USB core drivers;
  - DesignWare USB2 driver;
  - DesignWare USB3 driver;
  - USB Gadget drivers;
  - USB Serial drivers;
  - USB Mass Storage drivers;
  - USB Type-C suppor…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oem-7.0, Ubuntu:26.04:LTS: linux-oracle&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - Network file systems library;
  - Stream parser;
  - ARM64 architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Android drivers;
  - Bluetooth drivers;
  - TPM device driver;
  - DPLL subsystem;
  - EDAC drivers;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - IIO subsystem;
  - IIO ADC drivers;
  - InfiniBand drivers;
  - Input Device (Miscellaneous) drivers;
  - Multiple devices driver;
  - MemoryStick subsystem;
  - MMC subsystem;
  - MTD block device drivers;
  - Network drivers;
  - Ethernet bonding driver;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - Ethernet team driver;
  - MediaTek network drivers;
  - NVME drivers;
  - Device tree and open firmware driver;
  - Power sequencing drivers;
  - Voltage and Current Regulator drivers;
  - Real Time Clock drivers;
  - SCSI subsystem;
  - Greybus lights staging drivers;
  - Trusted Execution Environment drivers;
  - Thunderbolt and USB4 drivers;
  - TTY drivers;
  - Cadence USB3 driver;
  - USB Device Class drivers;
  - USB core drivers;
  - DesignWare USB2 driver;
  - DesignWare USB3 driver;
  - USB Gadget drivers;
  - USB Serial drivers;
  - USB Mass Storage drivers;
  - USB Type-C suppor…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-9018-1</guid>
    </item>
  </channel>
</rss>
