CVE-2023-53668: ring-buffer: Fix deadloop issue on reading trace_pipe
Noroxi assessment
Priority: Monitor (action score 28/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.15% (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 0a29dae5786d263016a9aceb1e56bf3fd4cc6fa0, 27bdd93e44cc28dd9b94893fae146b83d4f5b31e, 5e68f1f3a20fe9b6bde018e353269fbfa289609c.
Low priority for now. Upgrade to Linux Linux 0a29dae5786d263016a9aceb1e56bf3fd4cc6fa0, 27bdd93e44cc28dd9b94893fae146b83d4f5b31e, 5e68f1f3a20fe9b6bde018e353269fbfa289609c 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: Fix deadloop issue on reading trace_pipe Soft lockup occurs when reading file 'trace_pipe': watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [cat:4488] [...] RIP: 0010:ring_buffer_empty_cpu+0xed/0x170 RSP: 0018:ffff88810dd6fc48 EFLAGS: 00000246 RAX: 0000000000000000 RBX: 0000000000000246 RCX: ffffffff93d1aaeb RDX: ffff88810a280040 RSI: 0000000000000008 RDI: ffff88811164b218 RBP: ffff88811164b218 R08: 0000000000000000 R09: ffff88815156600f R10: ffffed102a2acc01 R11: 0000000000000001 R12: 0000000051651901 R13: 0000000000000000 R14: ffff888115e49500 R15: 0000000000000000 [...] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f8d853c2000 CR3: 000000010dcd8000 CR4: 00000000000006e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: __find_next_entry+0x1a8/0x4b0 ? peek_next_entry+0x250/0x250 ? down_write+0xa5/0x120 ? down_write_killable+0x130/0x130 trace_find_next_entry_inc+0x3b/0x1d0 tracing_read_pipe+0x423/0xae0 ? tracing_splice_read_pipe+0xcb0/0xcb0 vfs_read+0x16b/0x490 ksys_read+0x105/0x210 ? __ia32_sys_pwrite64+0x200/0x200 ? switch_fpu_return+0x108/0x220 do_syscall_64+0x33/0x40 entry_SYSCALL_64_after_hwframe+0x61/0xc6 Through the vmcore, I found it's because in tracing_read_pipe(), ring_buffer_empty_cpu() found some buffer is not empty but then it cannot read anything due to "rb_num_of_entries() == 0" always true, Then it infinitely loop the procedure due to user buffer not been filled, see following code path: tracing_read_pipe() { ... ... waitagain: tracing_wait_pipe() // 1. find non-empty buffer here trace_find_next_entry_inc() // 2. loop here try to find an entry __find_next_entry() ring_buffer_empty_cpu(); // 3. find non-empty buffer peek_next_entry() // 4. but peek always return NULL ring_buffer_peek() rb_buffer_peek() rb_get_reader_page() // 5. because rb_num_of_entries() == 0 always true here // then return NULL // 6. user buffer not been filled so goto 'waitgain' // and eventually leads to an deadloop in kernel!!! } By some analyzing, I found that when resetting ringbuffer, the 'entries' of its pages are not all cleared (see rb_reset_cpu()). Then when reducing the ringbuffer, and if some reduced pages exist dirty 'entries' data, they will be added into 'cpu_buffer->overrun' (see rb_remove_pages()), which cause wrong 'overrun' count and eventually cause the deadloop issue. To fix it, we need to clear every pages in rb_reset_cpu().
- Published
- Oct 7, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- CWE-125
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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
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 helpAffected 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.6 and later · before 4.14.322
- linux linux kernel4.15 and later · before 4.19.291
- linux linux kernel4.20 and later · before 5.4.251
- linux linux kernel5.5 and later · before 5.10.188
- linux linux kernel5.11 and later · before 5.15.121
- linux linux kernel5.16 and later · before 6.1.40
- linux linux kernel6.2 and later · before 6.4.5
- linux linux kernel6.5
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.6affected
- a5fb833172eca69136e9ee1ada778e404086ab8a and later · before 0a29dae5786d263016a9aceb1e56bf3fd4cc6fa0affected · git
- a5fb833172eca69136e9ee1ada778e404086ab8a and later · before a55e8a3596048c2f7b574049aeb1885b5abba1ccaffected · git
- a5fb833172eca69136e9ee1ada778e404086ab8a and later · before e84829522fc72bb43556b31575731de0440ac0ddaffected · git
- a5fb833172eca69136e9ee1ada778e404086ab8a and later · before 5e68f1f3a20fe9b6bde018e353269fbfa289609caffected · git
- a5fb833172eca69136e9ee1ada778e404086ab8a and later · before bb14a93bccc92766b1d9302c6bcbea17d4bce306affected · git
- a5fb833172eca69136e9ee1ada778e404086ab8a and later · before 8b0b63fdac6b70a45614e7d4b30e5bbb93deb007affected · git
- a5fb833172eca69136e9ee1ada778e404086ab8a and later · before 27bdd93e44cc28dd9b94893fae146b83d4f5b31eaffected · git
- a5fb833172eca69136e9ee1ada778e404086ab8a and later · before 7e42907f3a7b4ce3a2d1757f6d78336984daf8f5affected · git
- before 3.6not affected · semver
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.52-1 | 6.1.52-1 |
| Debian:13 | linux | before 6.4.11-1 | 6.4.11-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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 KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2023-53666Oct 7, 2025 · ASoC: codecs: wcd938x: fix missing mbhc init error handling22Monitor
- ← EarlierCVE-2023-53667Oct 7, 2025 · net: cdc_ncm: Deal with too low values of dwNtbOutMaxSize22Monitor
- Later →CVE-2023-53670Oct 7, 2025 · nvme-core: fix dev_pm_qos memleak22Monitor
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 | 0a29dae5786d263016a9aceb1e56bf3fd4cc6fa0 | Vendor (CNA) |
| Linux Linux | 27bdd93e44cc28dd9b94893fae146b83d4f5b31e | Vendor (CNA) |
| Linux Linux | 5e68f1f3a20fe9b6bde018e353269fbfa289609c | Vendor (CNA) |
| Linux Linux | 7e42907f3a7b4ce3a2d1757f6d78336984daf8f5 | Vendor (CNA) |
| Linux Linux | 8b0b63fdac6b70a45614e7d4b30e5bbb93deb007 | Vendor (CNA) |
| Linux Linux | a55e8a3596048c2f7b574049aeb1885b5abba1cc | Vendor (CNA) |
| Linux Linux | bb14a93bccc92766b1d9302c6bcbea17d4bce306 | Vendor (CNA) |
| Linux Linux | e84829522fc72bb43556b31575731de0440ac0dd | Vendor (CNA) |
| debian:linux | 6.1.52-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 researchersFinders, 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
- none
- 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
- None
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/27bdd93e44cc28dd9b94893fae146b83d4f5b31e
- git.kernel.org/stable/c/5e68f1f3a20fe9b6bde018e353269fbfa289609c
- git.kernel.org/stable/c/7e42907f3a7b4ce3a2d1757f6d78336984daf8f5
- git.kernel.org/stable/c/8b0b63fdac6b70a45614e7d4b30e5bbb93deb007
- git.kernel.org/stable/c/a55e8a3596048c2f7b574049aeb1885b5abba1cc
- git.kernel.org/stable/c/bb14a93bccc92766b1d9302c6bcbea17d4bce306
- git.kernel.org/stable/c/e84829522fc72bb43556b31575731de0440ac0dd
Vendor advisories and official records. Exploit/PoC links are deliberately left out.