<?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://vulnerability.circl.lu</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>Mon, 28 Sep 2026 19:51:01 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-56585 — LoongArch: Fix sleeping in atomic context for PREEMPT_RT</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-56585</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;LoongArch: Fix sleeping in atomic context for PREEMPT_RT&lt;/p&gt;
&lt;p&gt;Commit bab1c299f3945ffe79 (&amp;#34;LoongArch: Fix sleeping in atomic context in
setup_tlb_handler()&amp;#34;) changes the gfp flag from GFP_KERNEL to GFP_ATOMIC
for alloc_pages_node(). However, for PREEMPT_RT kernels we can still get
a &amp;#34;sleeping in atomic context&amp;#34; error:&lt;/p&gt;
&lt;p&gt;[    0.372259] BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48
[    0.372266] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 0, name: swapper/1
[    0.372268] preempt_count: 1, expected: 0
[    0.372270] RCU nest depth: 1, expected: 1
[    0.372272] 3 locks held by swapper/1/0:
[    0.372274]  #0: 900000000c9f5e60 (&amp;amp;pcp-&amp;gt;lock){+.+.}-{3:3}, at: get_page_from_freelist+0x524/0x1c60
[    0.372294]  #1: 90000000087013b8 (rcu_read_lock){....}-{1:3}, at: rt_spin_trylock+0x50/0x140
[    0.372305]  #2: 900000047fffd388 (&amp;amp;zone-&amp;gt;lock){+.+.}-{3:3}, at: __rmqueue_pcplist+0x30c/0xea0
[    0.372314] irq event stamp: 0
[    0.372316] hardirqs last  enabled at (0): [&amp;lt;0000000000000000&amp;gt;] 0x0
[    0.372322] hardirqs last disabled at (0): [&amp;lt;9000000005947320&amp;gt;] copy_process+0x9c0/0x26e0
[    0.372329] softirqs last  enabled at (0): [&amp;lt;9000000005947320&amp;gt;] copy_process+0x9c0/0x26e0
[    0.372335] softirqs last disabled at (0): [&amp;lt;0000000000000000&amp;gt;] 0x0
[    0.372341] CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Not tainted 6.12.0-rc7+ #1891
[    0.372346] Hardware name: Loongson Loongson…&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;LoongArch: Fix sleeping in atomic context for PREEMPT_RT&lt;/p&gt;
&lt;p&gt;Commit bab1c299f3945ffe79 (&amp;#34;LoongArch: Fix sleeping in atomic context in
setup_tlb_handler()&amp;#34;) changes the gfp flag from GFP_KERNEL to GFP_ATOMIC
for alloc_pages_node(). However, for PREEMPT_RT kernels we can still get
a &amp;#34;sleeping in atomic context&amp;#34; error:&lt;/p&gt;
&lt;p&gt;[    0.372259] BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48
[    0.372266] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 0, name: swapper/1
[    0.372268] preempt_count: 1, expected: 0
[    0.372270] RCU nest depth: 1, expected: 1
[    0.372272] 3 locks held by swapper/1/0:
[    0.372274]  #0: 900000000c9f5e60 (&amp;amp;pcp-&amp;gt;lock){+.+.}-{3:3}, at: get_page_from_freelist+0x524/0x1c60
[    0.372294]  #1: 90000000087013b8 (rcu_read_lock){....}-{1:3}, at: rt_spin_trylock+0x50/0x140
[    0.372305]  #2: 900000047fffd388 (&amp;amp;zone-&amp;gt;lock){+.+.}-{3:3}, at: __rmqueue_pcplist+0x30c/0xea0
[    0.372314] irq event stamp: 0
[    0.372316] hardirqs last  enabled at (0): [&amp;lt;0000000000000000&amp;gt;] 0x0
[    0.372322] hardirqs last disabled at (0): [&amp;lt;9000000005947320&amp;gt;] copy_process+0x9c0/0x26e0
[    0.372329] softirqs last  enabled at (0): [&amp;lt;9000000005947320&amp;gt;] copy_process+0x9c0/0x26e0
[    0.372335] softirqs last disabled at (0): [&amp;lt;0000000000000000&amp;gt;] 0x0
[    0.372341] CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Not tainted 6.12.0-rc7+ #1891
[    0.372346] Hardware name: Loongson Loongson…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-56585</guid>
    </item>
  </channel>
</rss>
