<?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>Thu, 15 Oct 2026 22:11:10 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-42239 — bpf: Fail bpf_timer_cancel when callback is being cancelled</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-42239</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;bpf: Fail bpf_timer_cancel when callback is being cancelled&lt;/p&gt;
&lt;p&gt;Given a schedule:&lt;/p&gt;
&lt;p&gt;timer1 cb			timer2 cb&lt;/p&gt;
&lt;p&gt;bpf_timer_cancel(timer2);	bpf_timer_cancel(timer1);&lt;/p&gt;
&lt;p&gt;Both bpf_timer_cancel calls would wait for the other callback to finish
executing, introducing a lockup.&lt;/p&gt;
&lt;p&gt;Add an atomic_t count named &amp;#39;cancelling&amp;#39; in bpf_hrtimer. This keeps
track of all in-flight cancellation requests for a given BPF timer.
Whenever cancelling a BPF timer, we must check if we have outstanding
cancellation requests, and if so, we must fail the operation with an
error (-EDEADLK) since cancellation is synchronous and waits for the
callback to finish executing. This implies that we can enter a deadlock
situation involving two or more timer callbacks executing in parallel
and attempting to cancel one another.&lt;/p&gt;
&lt;p&gt;Note that we avoid incrementing the cancelling counter for the target
timer (the one being cancelled) if bpf_timer_cancel is not invoked from
a callback, to avoid spurious errors. The whole point of detecting
cur-&amp;gt;cancelling and returning -EDEADLK is to not enter a busy wait loop
(which may or may not lead to a lockup). This does not apply in case the
caller is in a non-callback context, the other side can continue to
cancel as it sees fit without running into errors.&lt;/p&gt;
&lt;p&gt;Background on prior attempts:&lt;/p&gt;
&lt;p&gt;Earlier versions of this patch used a bool &amp;#39;cancelling&amp;#39; bit and used the
following pattern under timer-&amp;gt;lock to publish cancellation statu…&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;bpf: Fail bpf_timer_cancel when callback is being cancelled&lt;/p&gt;
&lt;p&gt;Given a schedule:&lt;/p&gt;
&lt;p&gt;timer1 cb			timer2 cb&lt;/p&gt;
&lt;p&gt;bpf_timer_cancel(timer2);	bpf_timer_cancel(timer1);&lt;/p&gt;
&lt;p&gt;Both bpf_timer_cancel calls would wait for the other callback to finish
executing, introducing a lockup.&lt;/p&gt;
&lt;p&gt;Add an atomic_t count named &amp;#39;cancelling&amp;#39; in bpf_hrtimer. This keeps
track of all in-flight cancellation requests for a given BPF timer.
Whenever cancelling a BPF timer, we must check if we have outstanding
cancellation requests, and if so, we must fail the operation with an
error (-EDEADLK) since cancellation is synchronous and waits for the
callback to finish executing. This implies that we can enter a deadlock
situation involving two or more timer callbacks executing in parallel
and attempting to cancel one another.&lt;/p&gt;
&lt;p&gt;Note that we avoid incrementing the cancelling counter for the target
timer (the one being cancelled) if bpf_timer_cancel is not invoked from
a callback, to avoid spurious errors. The whole point of detecting
cur-&amp;gt;cancelling and returning -EDEADLK is to not enter a busy wait loop
(which may or may not lead to a lockup). This does not apply in case the
caller is in a non-callback context, the other side can continue to
cancel as it sees fit without running into errors.&lt;/p&gt;
&lt;p&gt;Background on prior attempts:&lt;/p&gt;
&lt;p&gt;Earlier versions of this patch used a bool &amp;#39;cancelling&amp;#39; bit and used the
following pattern under timer-&amp;gt;lock to publish cancellation statu…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-42239</guid>
    </item>
    <item>
      <title>USN-7089-1 — linux, linux-gcp-6.8, linux-hwe-6.8 vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-7089-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-gcp-6.8, Ubuntu:22.04:LTS: linux-hwe-6.8, Ubuntu:24.04:LTS: linux&lt;/p&gt;
&lt;p&gt;Chenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel
did not properly check for the device to be enabled before writing. A local
attacker could possibly use this to cause a denial of service. (CVE-2024-25741)&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:
  - ARM32 architecture;
  - MIPS architecture;
  - PA-RISC architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Cryptographic API;
  - Serial ATA and Parallel ATA drivers;
  - Null block device driver;
  - Bluetooth drivers;
  - Cdrom driver;
  - Clock framework and drivers;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - Cirrus firmware drivers;
  - GPIO subsystem;
  - GPU drivers;
  - I2C subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - ISDN/mISDN subsystem;
  - LED subsystem;
  - Multiple devices driver;
  - Media drivers;
  - Fastrpc Driver;
  - Network drivers;
  - Microsoft Azure Network Adapter (MANA) driver;
  - Near Field Communication (NFC) drivers;
  - NVME drivers;
  - NVMEM (Non Volatile Memory) drivers;
  - PCI subsystem;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - S/390 drivers;
  - SCSI drivers;
  - Thermal drivers;
  - TTY drivers;
  - UFS subsystem;
  - USB DSL drivers;
  - USB core drivers;
  - DesignWare USB3 driver;
  - USB Gadget dr…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-gcp-6.8, Ubuntu:22.04:LTS: linux-hwe-6.8, Ubuntu:24.04:LTS: linux&lt;/p&gt;
&lt;p&gt;Chenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel
did not properly check for the device to be enabled before writing. A local
attacker could possibly use this to cause a denial of service. (CVE-2024-25741)&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:
  - ARM32 architecture;
  - MIPS architecture;
  - PA-RISC architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Cryptographic API;
  - Serial ATA and Parallel ATA drivers;
  - Null block device driver;
  - Bluetooth drivers;
  - Cdrom driver;
  - Clock framework and drivers;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - Cirrus firmware drivers;
  - GPIO subsystem;
  - GPU drivers;
  - I2C subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - ISDN/mISDN subsystem;
  - LED subsystem;
  - Multiple devices driver;
  - Media drivers;
  - Fastrpc Driver;
  - Network drivers;
  - Microsoft Azure Network Adapter (MANA) driver;
  - Near Field Communication (NFC) drivers;
  - NVME drivers;
  - NVMEM (Non Volatile Memory) drivers;
  - PCI subsystem;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - S/390 drivers;
  - SCSI drivers;
  - Thermal drivers;
  - TTY drivers;
  - UFS subsystem;
  - USB DSL drivers;
  - USB core drivers;
  - DesignWare USB3 driver;
  - USB Gadget dr…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-7089-1</guid>
    </item>
  </channel>
</rss>
