<?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://db.gcve.eu</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, 19 Nov 2026 17:17:48 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-50140 — sched/core: Disable page allocation in task_tick_mm_cid()</title>
      <link>https://db.gcve.eu/vuln/cve-2024-50140</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;sched/core: Disable page allocation in task_tick_mm_cid()&lt;/p&gt;
&lt;p&gt;With KASAN and PREEMPT_RT enabled, calling task_work_add() in
task_tick_mm_cid() may cause the following splat.&lt;/p&gt;
&lt;p&gt;[   63.696416] BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48
[   63.696416] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 610, name: modprobe
[   63.696416] preempt_count: 10001, expected: 0
[   63.696416] RCU nest depth: 1, expected: 1&lt;/p&gt;
&lt;p&gt;This problem is caused by the following call trace.&lt;/p&gt;
&lt;p&gt;sched_tick() [ acquire rq-&amp;gt;__lock ]
   -&amp;gt; task_tick_mm_cid()
    -&amp;gt; task_work_add()
     -&amp;gt; __kasan_record_aux_stack()
      -&amp;gt; kasan_save_stack()
       -&amp;gt; stack_depot_save_flags()
        -&amp;gt; alloc_pages_mpol_noprof()
         -&amp;gt; __alloc_pages_noprof()
	  -&amp;gt; get_page_from_freelist()
	   -&amp;gt; rmqueue()
	    -&amp;gt; rmqueue_pcplist()
	     -&amp;gt; __rmqueue_pcplist()
	      -&amp;gt; rmqueue_bulk()
	       -&amp;gt; rt_spin_lock()&lt;/p&gt;
&lt;p&gt;The rq lock is a raw_spinlock_t. We can&amp;#39;t sleep while holding
it. IOW, we can&amp;#39;t call alloc_pages() in stack_depot_save_flags().&lt;/p&gt;
&lt;p&gt;The task_tick_mm_cid() function with its task_work_add() call was
introduced by commit 223baf9d17f2 (&amp;#34;sched: Fix performance regression
introduced by mm_cid&amp;#34;) in v6.4 kernel.&lt;/p&gt;
&lt;p&gt;Fortunately, there is a kasan_record_aux_stack_noalloc() variant that
calls stack_depot_save_flags() while not allowing it to allocate
new pages.  To allow task_tick_mm_cid() to use task_work without
pa…&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;sched/core: Disable page allocation in task_tick_mm_cid()&lt;/p&gt;
&lt;p&gt;With KASAN and PREEMPT_RT enabled, calling task_work_add() in
task_tick_mm_cid() may cause the following splat.&lt;/p&gt;
&lt;p&gt;[   63.696416] BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48
[   63.696416] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 610, name: modprobe
[   63.696416] preempt_count: 10001, expected: 0
[   63.696416] RCU nest depth: 1, expected: 1&lt;/p&gt;
&lt;p&gt;This problem is caused by the following call trace.&lt;/p&gt;
&lt;p&gt;sched_tick() [ acquire rq-&amp;gt;__lock ]
   -&amp;gt; task_tick_mm_cid()
    -&amp;gt; task_work_add()
     -&amp;gt; __kasan_record_aux_stack()
      -&amp;gt; kasan_save_stack()
       -&amp;gt; stack_depot_save_flags()
        -&amp;gt; alloc_pages_mpol_noprof()
         -&amp;gt; __alloc_pages_noprof()
	  -&amp;gt; get_page_from_freelist()
	   -&amp;gt; rmqueue()
	    -&amp;gt; rmqueue_pcplist()
	     -&amp;gt; __rmqueue_pcplist()
	      -&amp;gt; rmqueue_bulk()
	       -&amp;gt; rt_spin_lock()&lt;/p&gt;
&lt;p&gt;The rq lock is a raw_spinlock_t. We can&amp;#39;t sleep while holding
it. IOW, we can&amp;#39;t call alloc_pages() in stack_depot_save_flags().&lt;/p&gt;
&lt;p&gt;The task_tick_mm_cid() function with its task_work_add() call was
introduced by commit 223baf9d17f2 (&amp;#34;sched: Fix performance regression
introduced by mm_cid&amp;#34;) in v6.4 kernel.&lt;/p&gt;
&lt;p&gt;Fortunately, there is a kasan_record_aux_stack_noalloc() variant that
calls stack_depot_save_flags() while not allowing it to allocate
new pages.  To allow task_tick_mm_cid() to use task_work without
pa…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2024-50140</guid>
    </item>
    <item>
      <title>USN-7276-1 — linux, linux-lowlatency vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-7276-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.10: linux, Ubuntu:24.10: linux-lowlatency&lt;/p&gt;
&lt;p&gt;Attila Szász discovered that the HFS+ file system implementation in the
Linux Kernel contained a heap overflow vulnerability. An attacker could use
a specially crafted file system image that, when mounted, could cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2025-0927)&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;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - SuperH RISC architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Drivers core;
  - ATA over ethernet (AOE) driver;
  - RAM backed block device driver;
  - Network block device driver;
  - Ublk userspace block driver;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - TPM device driver;
  - Clock framework and drivers;
  - Data acquisition framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - DAX dirext access to differentiated memory framework;
  - Buffer Sharing and Synchronization framework;
  - EDAC drivers;
  - FireWire subsystem;
  - ARM SCMI message protocol;
  - ARM SCPI message protocol;
  - EFI core;
  - Qualcomm firmware drivers;
  - GPIO subsystem;…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.10: linux, Ubuntu:24.10: linux-lowlatency&lt;/p&gt;
&lt;p&gt;Attila Szász discovered that the HFS+ file system implementation in the
Linux Kernel contained a heap overflow vulnerability. An attacker could use
a specially crafted file system image that, when mounted, could cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2025-0927)&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;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - SuperH RISC architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Drivers core;
  - ATA over ethernet (AOE) driver;
  - RAM backed block device driver;
  - Network block device driver;
  - Ublk userspace block driver;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - TPM device driver;
  - Clock framework and drivers;
  - Data acquisition framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - DAX dirext access to differentiated memory framework;
  - Buffer Sharing and Synchronization framework;
  - EDAC drivers;
  - FireWire subsystem;
  - ARM SCMI message protocol;
  - ARM SCPI message protocol;
  - EFI core;
  - Qualcomm firmware drivers;
  - GPIO subsystem;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-7276-1</guid>
    </item>
  </channel>
</rss>
