<?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>Fri, 02 Oct 2026 00:44:15 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53587 — ring-buffer: Sync IRQ works before buffer destruction</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53587</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;ring-buffer: Sync IRQ works before buffer destruction&lt;/p&gt;
&lt;p&gt;If something was written to the buffer just before destruction,
it may be possible (maybe not in a real system, but it did
happen in ARCH=um with time-travel) to destroy the ringbuffer
before the IRQ work ran, leading this KASAN report (or a crash
without KASAN):&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in irq_work_run_list+0x11a/0x13a
    Read of size 8 at addr 000000006d640a48 by task swapper/0&lt;/p&gt;
&lt;p&gt;CPU: 0 PID: 0 Comm: swapper Tainted: G        W  O       6.3.0-rc1 #7
    Stack:
     60c4f20f 0c203d48 41b58ab3 60f224fc
     600477fa 60f35687 60c4f20f 601273dd
     00000008 6101eb00 6101eab0 615be548
    Call Trace:
     [&amp;lt;60047a58&amp;gt;] show_stack+0x25e/0x282
     [&amp;lt;60c609e0&amp;gt;] dump_stack_lvl+0x96/0xfd
     [&amp;lt;60c50d4c&amp;gt;] print_report+0x1a7/0x5a8
     [&amp;lt;603078d3&amp;gt;] kasan_report+0xc1/0xe9
     [&amp;lt;60308950&amp;gt;] __asan_report_load8_noabort+0x1b/0x1d
     [&amp;lt;60232844&amp;gt;] irq_work_run_list+0x11a/0x13a
     [&amp;lt;602328b4&amp;gt;] irq_work_tick+0x24/0x34
     [&amp;lt;6017f9dc&amp;gt;] update_process_times+0x162/0x196
     [&amp;lt;6019f335&amp;gt;] tick_sched_handle+0x1a4/0x1c3
     [&amp;lt;6019fd9e&amp;gt;] tick_sched_timer+0x79/0x10c
     [&amp;lt;601812b9&amp;gt;] __hrtimer_run_queues.constprop.0+0x425/0x695
     [&amp;lt;60182913&amp;gt;] hrtimer_interrupt+0x16c/0x2c4
     [&amp;lt;600486a3&amp;gt;] um_timer+0x164/0x183
     [...]&lt;/p&gt;
&lt;p&gt;Allocated by task 411:
     save_stack_trace+0x99/0xb5
     stack_trace_save+0x81/0x9b
     kasan_save_stack+0x2d/0x54
     kasan…&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;ring-buffer: Sync IRQ works before buffer destruction&lt;/p&gt;
&lt;p&gt;If something was written to the buffer just before destruction,
it may be possible (maybe not in a real system, but it did
happen in ARCH=um with time-travel) to destroy the ringbuffer
before the IRQ work ran, leading this KASAN report (or a crash
without KASAN):&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in irq_work_run_list+0x11a/0x13a
    Read of size 8 at addr 000000006d640a48 by task swapper/0&lt;/p&gt;
&lt;p&gt;CPU: 0 PID: 0 Comm: swapper Tainted: G        W  O       6.3.0-rc1 #7
    Stack:
     60c4f20f 0c203d48 41b58ab3 60f224fc
     600477fa 60f35687 60c4f20f 601273dd
     00000008 6101eb00 6101eab0 615be548
    Call Trace:
     [&amp;lt;60047a58&amp;gt;] show_stack+0x25e/0x282
     [&amp;lt;60c609e0&amp;gt;] dump_stack_lvl+0x96/0xfd
     [&amp;lt;60c50d4c&amp;gt;] print_report+0x1a7/0x5a8
     [&amp;lt;603078d3&amp;gt;] kasan_report+0xc1/0xe9
     [&amp;lt;60308950&amp;gt;] __asan_report_load8_noabort+0x1b/0x1d
     [&amp;lt;60232844&amp;gt;] irq_work_run_list+0x11a/0x13a
     [&amp;lt;602328b4&amp;gt;] irq_work_tick+0x24/0x34
     [&amp;lt;6017f9dc&amp;gt;] update_process_times+0x162/0x196
     [&amp;lt;6019f335&amp;gt;] tick_sched_handle+0x1a4/0x1c3
     [&amp;lt;6019fd9e&amp;gt;] tick_sched_timer+0x79/0x10c
     [&amp;lt;601812b9&amp;gt;] __hrtimer_run_queues.constprop.0+0x425/0x695
     [&amp;lt;60182913&amp;gt;] hrtimer_interrupt+0x16c/0x2c4
     [&amp;lt;600486a3&amp;gt;] um_timer+0x164/0x183
     [...]&lt;/p&gt;
&lt;p&gt;Allocated by task 411:
     save_stack_trace+0x99/0xb5
     stack_trace_save+0x81/0x9b
     kasan_save_stack+0x2d/0x54
     kasan…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53587</guid>
    </item>
  </channel>
</rss>
