<?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 08:22:04 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64047 — net: tls: fix off-by-one in sg_chain entry count for wrapped sk_msg ring</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-64047</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: tls: fix off-by-one in sg_chain entry count for wrapped sk_msg ring&lt;/p&gt;
&lt;p&gt;When an sk_msg scatterlist ring wraps (sg.end &amp;lt; sg.start),
tls_push_record() chains the tail portion of the ring to the head
using sg_chain(). An extra entry in the sg array is reserved for
this:&lt;/p&gt;
&lt;p&gt;struct sk_msg_sg {
        [...]
        /* The extra two elements:
         * 1) used for chaining the front and sections when the list becomes
         *    partitioned (e.g. end &amp;lt; start). The crypto APIs require the
         *    chaining;
         * 2) to chain tailer SG entries after the message.
         */
        struct scatterlist              data[MAX_MSG_FRAGS + 2];&lt;/p&gt;
&lt;p&gt;The current code uses MAX_SKB_FRAGS + 1 as the ring size:&lt;/p&gt;
&lt;p&gt;sg_chain(&amp;amp;msg_pl-&amp;gt;sg.data[msg_pl-&amp;gt;sg.start],
             MAX_SKB_FRAGS - msg_pl-&amp;gt;sg.start + 1,
             msg_pl-&amp;gt;sg.data);&lt;/p&gt;
&lt;p&gt;This places the chain pointer at&lt;/p&gt;
&lt;p&gt;sg_chain(data[start], (MAX_SKB_FRAGS - msg_start + 1) .. =
  &amp;amp;data[start] + (MAX_SKB_FRAGS - msg_start + 1) - 1 =
  data[start + (MAX_SKB_FRAGS - start + 1) - 1] =
  data[MAX_SKB_FRAGS]&lt;/p&gt;
&lt;p&gt;instead of the true last entry. This is likely due to a &amp;#34;race&amp;#34; of
the commit under Fixes landing close to
commit 031097d9e079 (&amp;#34;bpf: sk_msg, zap ingress queue on psock down&amp;#34;)&lt;/p&gt;
&lt;p&gt;Convert to ARRAY_SIZE and drop the data[start] / - start (as suggested
by Sabrina).&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: tls: fix off-by-one in sg_chain entry count for wrapped sk_msg ring&lt;/p&gt;
&lt;p&gt;When an sk_msg scatterlist ring wraps (sg.end &amp;lt; sg.start),
tls_push_record() chains the tail portion of the ring to the head
using sg_chain(). An extra entry in the sg array is reserved for
this:&lt;/p&gt;
&lt;p&gt;struct sk_msg_sg {
        [...]
        /* The extra two elements:
         * 1) used for chaining the front and sections when the list becomes
         *    partitioned (e.g. end &amp;lt; start). The crypto APIs require the
         *    chaining;
         * 2) to chain tailer SG entries after the message.
         */
        struct scatterlist              data[MAX_MSG_FRAGS + 2];&lt;/p&gt;
&lt;p&gt;The current code uses MAX_SKB_FRAGS + 1 as the ring size:&lt;/p&gt;
&lt;p&gt;sg_chain(&amp;amp;msg_pl-&amp;gt;sg.data[msg_pl-&amp;gt;sg.start],
             MAX_SKB_FRAGS - msg_pl-&amp;gt;sg.start + 1,
             msg_pl-&amp;gt;sg.data);&lt;/p&gt;
&lt;p&gt;This places the chain pointer at&lt;/p&gt;
&lt;p&gt;sg_chain(data[start], (MAX_SKB_FRAGS - msg_start + 1) .. =
  &amp;amp;data[start] + (MAX_SKB_FRAGS - msg_start + 1) - 1 =
  data[start + (MAX_SKB_FRAGS - start + 1) - 1] =
  data[MAX_SKB_FRAGS]&lt;/p&gt;
&lt;p&gt;instead of the true last entry. This is likely due to a &amp;#34;race&amp;#34; of
the commit under Fixes landing close to
commit 031097d9e079 (&amp;#34;bpf: sk_msg, zap ingress queue on psock down&amp;#34;)&lt;/p&gt;
&lt;p&gt;Convert to ARRAY_SIZE and drop the data[start] / - start (as suggested
by Sabrina).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-64047</guid>
    </item>
    <item>
      <title>USN-8575-1 — linux, linux-gcp, linux-gcp-fips, linux-gke, linux-gkeop, linux-hwe-5.15, linux-kvm, linux-lowlatency, linux-lowlatency…</title>
      <link>https://cve.radiocsirt.org/vuln/usn-8575-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:20.04:LTS: linux-hwe-5.15, Ubuntu:Pro:20.04:LTS: linux-lowlatency-hwe-5.15, Ubuntu:22.04:LTS: linux, Ubuntu:22.04:LTS: linux-gcp, Ubuntu:22.04:LTS: linux-gke, Ubuntu:22.04:LTS: linux-gkeop, Ubuntu:22.04:LTS: linux-kvm, Ubuntu:22.04:LTS: linux-lowlatency, Ubuntu:22.04:LTS: linux-xilinx-zynqmp, Ubuntu:Pro:Realtime:22.04:LTS: linux-realtime and 1 more&lt;/p&gt;
&lt;p&gt;Maxim Suhanov discovered that the NTFS file system implementation in the
Linux kernel did not properly validate file name length in certain
situations, leading to an out-of-bounds read. An attacker could use this to
construct a malicious NTFS image that, when mounted and operated on, could
expose sensitive information (kernel memory). (CVE-2023-45896)&lt;/p&gt;
&lt;p&gt;It was discovered that some AMD processors did not properly clear data in
the floating point divider unit during speculative execution. A local
attacker could use this to expose sensitive information. (CVE-2025-54505)&lt;/p&gt;
&lt;p&gt;It was discovered that some AMD Zen 2 processors did not properly isolate
shared resources in the operation cache. A local attacker could possibly
use this issue to corrupt instructions executed at a higher privilege
level, resulting in privilege escalation. (CVE-2025-54518)&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;
  - ARM64 architecture;
  - MIPS architecture;
  - PowerPC architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - ACPI drivers;
  - ATM drivers;
  - Drivers core;
  - Power management core;
  - DRBD Distributed Replicated Block Device drivers;
  - RNBD block device driver;
  - Bluetooth drivers;
  - Bus devices;
  - Character device driver;
  - TPM device driver;
  - Clocksource driv…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:20.04:LTS: linux-hwe-5.15, Ubuntu:Pro:20.04:LTS: linux-lowlatency-hwe-5.15, Ubuntu:22.04:LTS: linux, Ubuntu:22.04:LTS: linux-gcp, Ubuntu:22.04:LTS: linux-gke, Ubuntu:22.04:LTS: linux-gkeop, Ubuntu:22.04:LTS: linux-kvm, Ubuntu:22.04:LTS: linux-lowlatency, Ubuntu:22.04:LTS: linux-xilinx-zynqmp, Ubuntu:Pro:Realtime:22.04:LTS: linux-realtime and 1 more&lt;/p&gt;
&lt;p&gt;Maxim Suhanov discovered that the NTFS file system implementation in the
Linux kernel did not properly validate file name length in certain
situations, leading to an out-of-bounds read. An attacker could use this to
construct a malicious NTFS image that, when mounted and operated on, could
expose sensitive information (kernel memory). (CVE-2023-45896)&lt;/p&gt;
&lt;p&gt;It was discovered that some AMD processors did not properly clear data in
the floating point divider unit during speculative execution. A local
attacker could use this to expose sensitive information. (CVE-2025-54505)&lt;/p&gt;
&lt;p&gt;It was discovered that some AMD Zen 2 processors did not properly isolate
shared resources in the operation cache. A local attacker could possibly
use this issue to corrupt instructions executed at a higher privilege
level, resulting in privilege escalation. (CVE-2025-54518)&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;
  - ARM64 architecture;
  - MIPS architecture;
  - PowerPC architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - ACPI drivers;
  - ATM drivers;
  - Drivers core;
  - Power management core;
  - DRBD Distributed Replicated Block Device drivers;
  - RNBD block device driver;
  - Bluetooth drivers;
  - Bus devices;
  - Character device driver;
  - TPM device driver;
  - Clocksource driv…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-8575-1</guid>
    </item>
  </channel>
</rss>
