NVD / CVE Program· CNA Linux

CVE-2023-53587: ring-buffer: Sync IRQ works before buffer destruction

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 0a65165bd24ee9231191597b7c232376fcd70cdb, 1c99f65d6af2a454bfd5207b4f6a97c8474a1191, 2399b1fda025e939b6fb1ac94505bcf718534e65.

Low priority for now. Upgrade to Linux Linux 0a65165bd24ee9231191597b7c232376fcd70cdb, 1c99f65d6af2a454bfd5207b4f6a97c8474a1191, 2399b1fda025e939b6fb1ac94505bcf718534e65 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Sync IRQ works before buffer destruction 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): BUG: KASAN: slab-use-after-free in irq_work_run_list+0x11a/0x13a Read of size 8 at addr 000000006d640a48 by task swapper/0 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: [<60047a58>] show_stack+0x25e/0x282 [<60c609e0>] dump_stack_lvl+0x96/0xfd [<60c50d4c>] print_report+0x1a7/0x5a8 [<603078d3>] kasan_report+0xc1/0xe9 [<60308950>] __asan_report_load8_noabort+0x1b/0x1d [<60232844>] irq_work_run_list+0x11a/0x13a [<602328b4>] irq_work_tick+0x24/0x34 [<6017f9dc>] update_process_times+0x162/0x196 [<6019f335>] tick_sched_handle+0x1a4/0x1c3 [<6019fd9e>] tick_sched_timer+0x79/0x10c [<601812b9>] __hrtimer_run_queues.constprop.0+0x425/0x695 [<60182913>] hrtimer_interrupt+0x16c/0x2c4 [<600486a3>] um_timer+0x164/0x183 [...] Allocated by task 411: save_stack_trace+0x99/0xb5 stack_trace_save+0x81/0x9b kasan_save_stack+0x2d/0x54 kasan_set_track+0x34/0x3e kasan_save_alloc_info+0x25/0x28 ____kasan_kmalloc+0x8b/0x97 __kasan_kmalloc+0x10/0x12 __kmalloc+0xb2/0xe8 load_elf_phdrs+0xee/0x182 [...] The buggy address belongs to the object at 000000006d640800 which belongs to the cache kmalloc-1k of size 1024 The buggy address is located 584 bytes inside of freed 1024-byte region [000000006d640800, 000000006d640c00) Add the appropriate irq_work_sync() so the work finishes before the buffers are destroyed. Prior to the commit in the Fixes tag below, there was only a single global IRQ work, so this issue didn't exist.

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

BDU:2026-12404

Published: Oct 4, 2025
Updated: Oct 15, 2026
EPSS: 0.1% · 5th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 7.8
CNA · Linux: 7.8; agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernel3.10 and later · before 4.14.315
linux linux kernel4.15 and later · before 4.19.283
linux linux kernel4.20 and later · before 5.4.243
linux linux kernel5.5 and later · before 5.10.180
linux linux kernel5.11 and later · before 5.15.111
linux linux kernel5.16 and later · before 6.1.28
linux linux kernel6.2 and later · before 6.2.15
linux linux kernel6.3 and later · before 6.3.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 3.10affected
- 15693458c4bc0693fd63a50d60f35b628fcf4e29 and later · before 372c5ee537b8366b64b691ba29e9335525e1655eaffected · git
- 15693458c4bc0693fd63a50d60f35b628fcf4e29 and later · before 2702b67f59d455072a08dc40312f9b090d4dec04affected · git
- 15693458c4bc0693fd63a50d60f35b628fcf4e29 and later · before 2399b1fda025e939b6fb1ac94505bcf718534e65affected · git
- 15693458c4bc0693fd63a50d60f35b628fcf4e29 and later · before 1c99f65d6af2a454bfd5207b4f6a97c8474a1191affected · git
- 15693458c4bc0693fd63a50d60f35b628fcf4e29 and later · before c63741e872fcfb10e153517750f7908f0c00f60daffected · git
- 15693458c4bc0693fd63a50d60f35b628fcf4e29 and later · before d9834abd8b24d1fe8092859e436fe1e0fd467c61affected · git
- 15693458c4bc0693fd63a50d60f35b628fcf4e29 and later · before fc6858b7f8e1221f62ce8c6ff8a13a349c32cd76affected · git
- 15693458c4bc0693fd63a50d60f35b628fcf4e29 and later · before 0a65165bd24ee9231191597b7c232376fcd70cdbaffected · git
- 15693458c4bc0693fd63a50d60f35b628fcf4e29 and later · before 675751bb20634f981498c7d66161584080cc061eaffected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.1.37-1	6.1.37-1
Debian:13	linux	before 6.3.7-1	6.3.7-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2023-53566Oct 4, 2025 · netfilter: nft_set_rbtree: fix null deref on element insertion
22Monitor
← EarlierCVE-2023-53574Oct 4, 2025 · wifi: rtw88: delete timer and free skb queue when unloading
22Monitor
Later →CVE-2023-53589Oct 4, 2025 · wifi: iwlwifi: mvm: don't trust firmware n_channels
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	0a65165bd24ee9231191597b7c232376fcd70cdb	Vendor (CNA)
Linux Linux	1c99f65d6af2a454bfd5207b4f6a97c8474a1191	Vendor (CNA)
Linux Linux	2399b1fda025e939b6fb1ac94505bcf718534e65	Vendor (CNA)
Linux Linux	2702b67f59d455072a08dc40312f9b090d4dec04	Vendor (CNA)
Linux Linux	372c5ee537b8366b64b691ba29e9335525e1655e	Vendor (CNA)
Linux Linux	675751bb20634f981498c7d66161584080cc061e	Vendor (CNA)
Linux Linux	c63741e872fcfb10e153517750f7908f0c00f60d	Vendor (CNA)
Linux Linux	d9834abd8b24d1fe8092859e436fe1e0fd467c61	Vendor (CNA)
Linux Linux	fc6858b7f8e1221f62ce8c6ff8a13a349c32cd76	Vendor (CNA)
debian:linux	6.1.37-1 · Debian:12	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

SSVC exploitation— → noneOct 15, 2026, 11:07 PM UTC
Fix✗ → ✓Sep 28, 2026, 10:11 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/0a65165bd24ee9231191597b7c232376fcd70cdb

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records