<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-14T17:34:34.343294+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2025-21979</id>
    <title>CVE-2025-21979 — wifi: cfg80211: cancel wiphy_work before freeing wiphy</title>
    <updated>2026-10-14T17:34:34.369500+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>wifi: cfg80211: cancel wiphy_work before freeing wiphy</p>
<p>A wiphy_work can be queued from the moment the wiphy is allocated and
initialized (i.e. wiphy_new_nm). When a wiphy_work is queued, the
rdev::wiphy_work is getting queued.</p>
<p>If wiphy_free is called before the rdev::wiphy_work had a chance to run,
the wiphy memory will be freed, and then when it eventally gets to run
it'll use invalid memory.</p>
<p>Fix this by canceling the work before freeing the wiphy.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2025-21979"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/usn-7605-1</id>
    <title>USN-7605-1 — linux, linux-aws, linux-gcp, linux-gcp-6.11, linux-hwe-6.11, linux-oracle, linux-raspi, linux-realtime vulnerabilities</title>
    <updated>2026-10-14T17:34:34.369573+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:24.04:LTS: linux-gcp-6.11, Ubuntu:24.04:LTS: linux-hwe-6.11</p>
<p>It was discovered that the CIFS network file system implementation in the
Linux kernel did not properly verify the target namespace when handling
upcalls. An attacker could use this to expose sensitive information.
(CVE-2025-2312)</p>
<p>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;
  - ARM64 architecture;
  - PowerPC architecture;
  - x86 architecture;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Ublk userspace block driver;
  - Compressed RAM block device driver;
  - Bus devices;
  - AMD CDX bus driver;
  - Clock framework and drivers;
  - DMA engine subsystem;
  - DPLL subsystem;
  - Qualcomm firmware drivers;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - Multiple devices driver;
  - Media drivers;
  - MemoryStick subsystem;
  - Network drivers;
  - Mellanox network drivers;
  - NTB driver;
  - NVME drivers;
  - PCI subsystem;
  - Pin controllers subsystem;
  - RapidIO drivers;
  - Voltage and Current Regulator drivers;
  - Remote Processor subsystem;
  - SCSI subsystem;
  - SLIMbus drivers;
  - QCOM SoC drivers;
  - VideoCore services drivers;
  - Thermal drivers;
  - USB DSL drivers;
  - USB Host Controller drivers;
  - Renesas USBHS Controller drivers;
  - USB Type-C Connector System Software Interface driver;
  - Virtio Host (VHOST) subsystem;
  - Fr…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/usn-7605-1"/>
  </entry>
</feed>
