<?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 10:53:12 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38512 — wifi: prevent A-MSDU attacks in mesh networks</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-38512</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;wifi: prevent A-MSDU attacks in mesh networks&lt;/p&gt;
&lt;p&gt;This patch is a mitigation to prevent the A-MSDU spoofing vulnerability
for mesh networks. The initial update to the IEEE 802.11 standard, in
response to the FragAttacks, missed this case (CVE-2025-27558). It can
be considered a variant of CVE-2020-24588 but for mesh networks.&lt;/p&gt;
&lt;p&gt;This patch tries to detect if a standard MSDU was turned into an A-MSDU
by an adversary. This is done by parsing a received A-MSDU as a standard
MSDU, calculating the length of the Mesh Control header, and seeing if
the 6 bytes after this header equal the start of an rfc1042 header. If
equal, this is a strong indication of an ongoing attack attempt.&lt;/p&gt;
&lt;p&gt;This defense was tested with mac80211_hwsim against a mesh network that
uses an empty Mesh Address Extension field, i.e., when four addresses
are used, and when using a 12-byte Mesh Address Extension field, i.e.,
when six addresses are used. Functionality of normal MSDUs and A-MSDUs
was also tested, and confirmed working, when using both an empty and
12-byte Mesh Address Extension field.&lt;/p&gt;
&lt;p&gt;It was also tested with mac80211_hwsim that A-MSDU attacks in non-mesh
networks keep being detected and prevented.&lt;/p&gt;
&lt;p&gt;Note that the vulnerability being patched, and the defense being
implemented, was also discussed in the following paper and in the
following IEEE 802.11 presentation:&lt;/p&gt;
&lt;p&gt;https://papers.mathyvanhoef.com/wisec2025.pdf
https://mentor.ieee.org/802.1…&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;wifi: prevent A-MSDU attacks in mesh networks&lt;/p&gt;
&lt;p&gt;This patch is a mitigation to prevent the A-MSDU spoofing vulnerability
for mesh networks. The initial update to the IEEE 802.11 standard, in
response to the FragAttacks, missed this case (CVE-2025-27558). It can
be considered a variant of CVE-2020-24588 but for mesh networks.&lt;/p&gt;
&lt;p&gt;This patch tries to detect if a standard MSDU was turned into an A-MSDU
by an adversary. This is done by parsing a received A-MSDU as a standard
MSDU, calculating the length of the Mesh Control header, and seeing if
the 6 bytes after this header equal the start of an rfc1042 header. If
equal, this is a strong indication of an ongoing attack attempt.&lt;/p&gt;
&lt;p&gt;This defense was tested with mac80211_hwsim against a mesh network that
uses an empty Mesh Address Extension field, i.e., when four addresses
are used, and when using a 12-byte Mesh Address Extension field, i.e.,
when six addresses are used. Functionality of normal MSDUs and A-MSDUs
was also tested, and confirmed working, when using both an empty and
12-byte Mesh Address Extension field.&lt;/p&gt;
&lt;p&gt;It was also tested with mac80211_hwsim that A-MSDU attacks in non-mesh
networks keep being detected and prevented.&lt;/p&gt;
&lt;p&gt;Note that the vulnerability being patched, and the defense being
implemented, was also discussed in the following paper and in the
following IEEE 802.11 presentation:&lt;/p&gt;
&lt;p&gt;https://papers.mathyvanhoef.com/wisec2025.pdf
https://mentor.ieee.org/802.1…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-38512</guid>
    </item>
    <item>
      <title>USN-7879-1 — linux, linux-aws, linux-gcp, linux-hwe-6.14, linux-oracle, linux-realtime vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-7879-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-6.14&lt;/p&gt;
&lt;p&gt;It was discovered that improper initialization of CPU cache memory could
allow a local attacker with hypervisor access to overwrite SEV-SNP guest
memory resulting in loss of data integrity. (CVE-2024-36331)&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:
  - ARM64 architecture;
  - PowerPC architecture;
  - S390 architecture;
  - x86 architecture;
  - Network block device driver;
  - Character device driver;
  - Clock framework and drivers;
  - Data acquisition framework and drivers;
  - Hardware crypto device drivers;
  - Device frequency scaling framework;
  - DMA engine subsystem;
  - EDAC drivers;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - IIO subsystem;
  - IIO ADC drivers;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Multiple devices driver;
  - Media drivers;
  - Network drivers;
  - Mellanox network drivers;
  - PCI subsystem;
  - PHY drivers;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - Power supply drivers;
  - Powercap sysfs driver;
  - Voltage and Current Regulator drivers;
  - S/390 drivers;
  - ASPEED SoC drivers;
  - SPI subsystem;
  - small TFT LCD display modules;
  - Media staging drivers;
  - USB Gadget drivers;
  - vDPA drivers;
  - VFIO drivers;
  - Framebuffer layer;
  - Xen hypervisor drivers;
  - BTRFS file system;
  - Ceph distributed file sy…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-6.14&lt;/p&gt;
&lt;p&gt;It was discovered that improper initialization of CPU cache memory could
allow a local attacker with hypervisor access to overwrite SEV-SNP guest
memory resulting in loss of data integrity. (CVE-2024-36331)&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:
  - ARM64 architecture;
  - PowerPC architecture;
  - S390 architecture;
  - x86 architecture;
  - Network block device driver;
  - Character device driver;
  - Clock framework and drivers;
  - Data acquisition framework and drivers;
  - Hardware crypto device drivers;
  - Device frequency scaling framework;
  - DMA engine subsystem;
  - EDAC drivers;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - IIO subsystem;
  - IIO ADC drivers;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Multiple devices driver;
  - Media drivers;
  - Network drivers;
  - Mellanox network drivers;
  - PCI subsystem;
  - PHY drivers;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - Power supply drivers;
  - Powercap sysfs driver;
  - Voltage and Current Regulator drivers;
  - S/390 drivers;
  - ASPEED SoC drivers;
  - SPI subsystem;
  - small TFT LCD display modules;
  - Media staging drivers;
  - USB Gadget drivers;
  - vDPA drivers;
  - VFIO drivers;
  - Framebuffer layer;
  - Xen hypervisor drivers;
  - BTRFS file system;
  - Ceph distributed file sy…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-7879-1</guid>
    </item>
  </channel>
</rss>
