<?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 01:13:44 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38023 — nfs: handle failure of nfs_get_lock_context in unlock path</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-38023</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;nfs: handle failure of nfs_get_lock_context in unlock path&lt;/p&gt;
&lt;p&gt;When memory is insufficient, the allocation of nfs_lock_context in
nfs_get_lock_context() fails and returns -ENOMEM. If we mistakenly treat
an nfs4_unlockdata structure (whose l_ctx member has been set to -ENOMEM)
as valid and proceed to execute rpc_run_task(), this will trigger a NULL
pointer dereference in nfs4_locku_prepare. For example:&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 000000000000000c
PGD 0 P4D 0
Oops: Oops: 0000 [#1] SMP PTI
CPU: 15 UID: 0 PID: 12 Comm: kworker/u64:0 Not tainted 6.15.0-rc2-dirty #60
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-2.fc40
Workqueue: rpciod rpc_async_schedule
RIP: 0010:nfs4_locku_prepare+0x35/0xc2
Code: 89 f2 48 89 fd 48 c7 c7 68 69 ef b5 53 48 8b 8e 90 00 00 00 48 89 f3
RSP: 0018:ffffbbafc006bdb8 EFLAGS: 00010246
RAX: 000000000000004b RBX: ffff9b964fc1fa00 RCX: 0000000000000000
RDX: 0000000000000000 RSI: fffffffffffffff4 RDI: ffff9ba53fddbf40
RBP: ffff9ba539934000 R08: 0000000000000000 R09: ffffbbafc006bc38
R10: ffffffffb6b689c8 R11: 0000000000000003 R12: ffff9ba539934030
R13: 0000000000000001 R14: 0000000004248060 R15: ffffffffb56d1c30
FS: 0000000000000000(0000) GS:ffff9ba5881f0000(0000) knlGS:00000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000000000c CR3: 000000093f244000 CR4: 00000000000006f0
Call Trace:
 &amp;lt;TASK&amp;gt;
 __rpc_execute+0xbc/0x480
 rpc_async_sched…&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;nfs: handle failure of nfs_get_lock_context in unlock path&lt;/p&gt;
&lt;p&gt;When memory is insufficient, the allocation of nfs_lock_context in
nfs_get_lock_context() fails and returns -ENOMEM. If we mistakenly treat
an nfs4_unlockdata structure (whose l_ctx member has been set to -ENOMEM)
as valid and proceed to execute rpc_run_task(), this will trigger a NULL
pointer dereference in nfs4_locku_prepare. For example:&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 000000000000000c
PGD 0 P4D 0
Oops: Oops: 0000 [#1] SMP PTI
CPU: 15 UID: 0 PID: 12 Comm: kworker/u64:0 Not tainted 6.15.0-rc2-dirty #60
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-2.fc40
Workqueue: rpciod rpc_async_schedule
RIP: 0010:nfs4_locku_prepare+0x35/0xc2
Code: 89 f2 48 89 fd 48 c7 c7 68 69 ef b5 53 48 8b 8e 90 00 00 00 48 89 f3
RSP: 0018:ffffbbafc006bdb8 EFLAGS: 00010246
RAX: 000000000000004b RBX: ffff9b964fc1fa00 RCX: 0000000000000000
RDX: 0000000000000000 RSI: fffffffffffffff4 RDI: ffff9ba53fddbf40
RBP: ffff9ba539934000 R08: 0000000000000000 R09: ffffbbafc006bc38
R10: ffffffffb6b689c8 R11: 0000000000000003 R12: ffff9ba539934030
R13: 0000000000000001 R14: 0000000004248060 R15: ffffffffb56d1c30
FS: 0000000000000000(0000) GS:ffff9ba5881f0000(0000) knlGS:00000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000000000c CR3: 000000093f244000 CR4: 00000000000006f0
Call Trace:
 &amp;lt;TASK&amp;gt;
 __rpc_execute+0xbc/0x480
 rpc_async_sched…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-38023</guid>
    </item>
    <item>
      <title>USN-7654-1 — linux, linux-aws, linux-aws-5.15, linux-gcp, linux-gcp-5.15, linux-gke, linux-gkeop, linux-hwe-5.15, linux-ibm, linux-i…</title>
      <link>https://cve.radiocsirt.org/vuln/usn-7654-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:20.04:LTS: linux-aws-5.15, Ubuntu:Pro:20.04:LTS: linux-gcp-5.15, Ubuntu:Pro:20.04:LTS: linux-hwe-5.15, Ubuntu:Pro:20.04:LTS: linux-ibm-5.15, Ubuntu:Pro:20.04:LTS: linux-lowlatency-hwe-5.15, Ubuntu:Pro:20.04:LTS: linux-nvidia-tegra-5.15, Ubuntu:Pro:20.04:LTS: linux-oracle-5.15, Ubuntu:22.04:LTS: linux, Ubuntu:22.04:LTS: linux-aws, Ubuntu:22.04:LTS: linux-gcp and 9 more&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:
  - PA-RISC architecture;
  - PowerPC architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Serial ATA and Parallel ATA drivers;
  - Bluetooth drivers;
  - Bus devices;
  - CPU frequency scaling framework;
  - Buffer Sharing and Synchronization framework;
  - DMA engine subsystem;
  - ARM SCMI message protocol;
  - GPU drivers;
  - HID subsystem;
  - HSI subsystem;
  - I2C subsystem;
  - I3C subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - IRQ chip drivers;
  - MCB driver;
  - Multiple devices driver;
  - Media drivers;
  - Multifunction device drivers;
  - PCI Endpoint Test driver;
  - MTD block device drivers;
  - Network drivers;
  - Device tree and open firmware driver;
  - PCI subsystem;
  - TI SCI PM domains driver;
  - PWM drivers;
  - S/390 drivers;
  - SCSI subsystem;
  - Samsung SoC drivers;
  - TCM subsystem;
  - UFS subsystem;
  - Cadence USB3 driver;
  - ChipIdea USB driver;
  - USB Device Class drivers;
  - DesignWare USB3 driver;
  - USB Gadget drivers;
  - USB Type-C support driver;
  - USB Type-C Connector System Software Interface driver;
  - Backlight driver;
  - Framebuffer layer;
  - Xen hypervisor drivers;
  - BTRFS file system;
  - Ext4 file system;
  - F2FS file system;
  - File systems infrastructure;
  - JFS…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:20.04:LTS: linux-aws-5.15, Ubuntu:Pro:20.04:LTS: linux-gcp-5.15, Ubuntu:Pro:20.04:LTS: linux-hwe-5.15, Ubuntu:Pro:20.04:LTS: linux-ibm-5.15, Ubuntu:Pro:20.04:LTS: linux-lowlatency-hwe-5.15, Ubuntu:Pro:20.04:LTS: linux-nvidia-tegra-5.15, Ubuntu:Pro:20.04:LTS: linux-oracle-5.15, Ubuntu:22.04:LTS: linux, Ubuntu:22.04:LTS: linux-aws, Ubuntu:22.04:LTS: linux-gcp and 9 more&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:
  - PA-RISC architecture;
  - PowerPC architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Serial ATA and Parallel ATA drivers;
  - Bluetooth drivers;
  - Bus devices;
  - CPU frequency scaling framework;
  - Buffer Sharing and Synchronization framework;
  - DMA engine subsystem;
  - ARM SCMI message protocol;
  - GPU drivers;
  - HID subsystem;
  - HSI subsystem;
  - I2C subsystem;
  - I3C subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - IRQ chip drivers;
  - MCB driver;
  - Multiple devices driver;
  - Media drivers;
  - Multifunction device drivers;
  - PCI Endpoint Test driver;
  - MTD block device drivers;
  - Network drivers;
  - Device tree and open firmware driver;
  - PCI subsystem;
  - TI SCI PM domains driver;
  - PWM drivers;
  - S/390 drivers;
  - SCSI subsystem;
  - Samsung SoC drivers;
  - TCM subsystem;
  - UFS subsystem;
  - Cadence USB3 driver;
  - ChipIdea USB driver;
  - USB Device Class drivers;
  - DesignWare USB3 driver;
  - USB Gadget drivers;
  - USB Type-C support driver;
  - USB Type-C Connector System Software Interface driver;
  - Backlight driver;
  - Framebuffer layer;
  - Xen hypervisor drivers;
  - BTRFS file system;
  - Ext4 file system;
  - F2FS file system;
  - File systems infrastructure;
  - JFS…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-7654-1</guid>
    </item>
  </channel>
</rss>
