<?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-15T11:44:39.051931+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-2024-42096</id>
    <title>CVE-2024-42096 — x86: stop playing stack games in profile_pc()</title>
    <updated>2026-10-15T11:44:39.119647+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux, Siemens SIMATIC S7-1500 TM MFP - GNU/Linux subsystem, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>x86: stop playing stack games in profile_pc()</p>
<p>The 'profile_pc()' function is used for timer-based profiling, which
isn't really all that relevant any more to begin with, but it also ends
up making assumptions based on the stack layout that aren't necessarily
valid.</p>
<p>Basically, the code tries to account the time spent in spinlocks to the
caller rather than the spinlock, and while I support that as a concept,
it's not worth the code complexity or the KASAN warnings when no serious
profiling is done using timers anyway these days.</p>
<p>And the code really does depend on stack layout that is only true in the
simplest of cases.  We've lost the comment at some point (I think when
the 32-bit and 64-bit code was unified), but it used to say:</p>
<p>Assume the lock function has either no stack frame or a copy
	of eflags from PUSHF.</p>
<p>which explains why it just blindly loads a word or two straight off the
stack pointer and then takes a minimal look at the values to just check
if they might be eflags or the return pc:</p>
<p>Eflags always has bits 22 and up cleared unlike kernel addresses</p>
<p>but that basic stack layout assumption assumes that there isn't any lock
debugging etc going on that would complicate the code and cause a stack
frame.</p>
<p>It causes KASAN unhappiness reported for years by syzkaller [1] and
others [2].</p>
<p>With no real practical reason for this any more, just remove the code.</p>
<p>Just for historical interest, here's some…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2024-42096"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/usn-7003-1</id>
    <title>USN-7003-1 — linux, linux-aws, linux-azure, linux-bluefield, linux-gcp, linux-gkeop, linux-ibm, linux-kvm, linux-oracle vulnerabilit…</title>
    <updated>2026-10-15T11:44:39.119754+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:20.04:LTS: linux, Ubuntu:20.04:LTS: linux-aws, Ubuntu:20.04:LTS: linux-azure, Ubuntu:20.04:LTS: linux-bluefield, Ubuntu:20.04:LTS: linux-gcp, Ubuntu:20.04:LTS: linux-gkeop, Ubuntu:20.04:LTS: linux-ibm, Ubuntu:20.04:LTS: linux-kvm, Ubuntu:20.04:LTS: linux-oracle</p>
<p>It was discovered that the JFS file system contained an out-of-bounds read
vulnerability when printing xattr debug information. A local attacker could
use this to cause a denial of service (system crash). (CVE-2024-40902)</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:
  - MIPS architecture;
  - PowerPC architecture;
  - x86 architecture;
  - ACPI drivers;
  - Serial ATA and Parallel ATA drivers;
  - Drivers core;
  - GPIO subsystem;
  - GPU drivers;
  - Greybus drivers;
  - HID subsystem;
  - I2C subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - Media drivers;
  - VMware VMCI Driver;
  - Network drivers;
  - Pin controllers subsystem;
  - S/390 drivers;
  - SCSI drivers;
  - USB subsystem;
  - JFFS2 file system;
  - JFS file system;
  - File systems infrastructure;
  - NILFS2 file system;
  - IOMMU subsystem;
  - Sun RPC protocol;
  - Netfilter;
  - Memory management;
  - B.A.T.M.A.N. meshing protocol;
  - CAN network layer;
  - Ceph Core library;
  - Networking core;
  - IPv4 networking;
  - IPv6 networking;
  - IUCV driver;
  - MAC80211 subsystem;
  - NET/ROM layer;
  - Network traffic control;
  - SoC Audio for Freescale CPUs drivers;
(CVE-2024-40905, CVE-2024-41095, CVE-2024-41035, CVE-2024-36974,
CVE-2024-40959, CVE-2024-40978, CVE-2024-42236, CVE-2024-40963,
CVE-2024-40916, CVE-2024-41006, CVE-2024-39495, CVE-2023-52803,
CVE-2024…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/usn-7003-1"/>
  </entry>
</feed>
