Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-54211: tracing: Fix warning in trace_buffered_event_disable()

—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 0/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.21% (FIRST EPSS).
  • Fixed version: Linux Linux 1488d782c9e43087a3f341b8186cd25f3cf75583, 528c9d73153754defb748f0b96ad33308668d817, 813cede7b2f5a4b1b75d2d4bb4e705cc8e063b20.

Low priority for now. Upgrade to Linux Linux 1488d782c9e43087a3f341b8186cd25f3cf75583, 528c9d73153754defb748f0b96ad33308668d817, 813cede7b2f5a4b1b75d2d4bb4e705cc8e063b20 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: tracing: Fix warning in trace_buffered_event_disable() Warning happened in trace_buffered_event_disable() at WARN_ON_ONCE(!trace_buffered_event_ref) Call Trace: ? __warn+0xa5/0x1b0 ? trace_buffered_event_disable+0x189/0x1b0 __ftrace_event_enable_disable+0x19e/0x3e0 free_probe_data+0x3b/0xa0 unregister_ftrace_function_probe_func+0x6b8/0x800 event_enable_func+0x2f0/0x3d0 ftrace_process_regex.isra.0+0x12d/0x1b0 ftrace_filter_write+0xe6/0x140 vfs_write+0x1c9/0x6f0 [...] The cause of the warning is in __ftrace_event_enable_disable(), trace_buffered_event_enable() was called once while trace_buffered_event_disable() was called twice. Reproduction script show as below, for analysis, see the comments: ``` #!/bin/bash cd /sys/kernel/tracing/ # 1. Register a 'disable_event' command, then: # 1) SOFT_DISABLED_BIT was set; # 2) trace_buffered_event_enable() was called first time; echo 'cmdline_proc_show:disable_event:initcall:initcall_finish' > \ set_ftrace_filter # 2. Enable the event registered, then: # 1) SOFT_DISABLED_BIT was cleared; # 2) trace_buffered_event_disable() was called first time; echo 1 > events/initcall/initcall_finish/enable # 3. Try to call into cmdline_proc_show(), then SOFT_DISABLED_BIT was # set again!!! cat /proc/cmdline # 4. Unregister the 'disable_event' command, then: # 1) SOFT_DISABLED_BIT was cleared again; # 2) trace_buffered_event_disable() was called second time!!! echo '!cmdline_proc_show:disable_event:initcall:initcall_finish' > \ set_ftrace_filter ``` To fix it, IIUC, we can change to call trace_buffered_event_enable() at fist time soft-mode enabled, and call trace_buffered_event_disable() at last time soft-mode disabled.

Published
Dec 30, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 11th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

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.

Follow CVE-2023-54211

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
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.

—

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

    • 4.7affected
    • 0fc1b09ff1ff404ddf753f5ffa5cd0adc8fdcdc9 and later · before 1488d782c9e43087a3f341b8186cd25f3cf75583affected · git
    • 0fc1b09ff1ff404ddf753f5ffa5cd0adc8fdcdc9 and later · before b4f4ab423107dc1ba8e9cc6488c645be6403d3f5affected · git
    • 0fc1b09ff1ff404ddf753f5ffa5cd0adc8fdcdc9 and later · before cdcc35e6454133feb61561b4e0d0c80e52cbc2baaffected · git
    • 0fc1b09ff1ff404ddf753f5ffa5cd0adc8fdcdc9 and later · before a6d2fd1703cdc8ecfc3e73987e0fb7474ae2b074affected · git
    • 0fc1b09ff1ff404ddf753f5ffa5cd0adc8fdcdc9 and later · before 813cede7b2f5a4b1b75d2d4bb4e705cc8e063b20affected · git
    • 0fc1b09ff1ff404ddf753f5ffa5cd0adc8fdcdc9 and later · before a3a3c7bddab9b6c5690b20796ef5e332b8c48afbaffected · git
    • 0fc1b09ff1ff404ddf753f5ffa5cd0adc8fdcdc9 and later · before 528c9d73153754defb748f0b96ad33308668d817affected · git
    • 0fc1b09ff1ff404ddf753f5ffa5cd0adc8fdcdc9 and later · before dea499781a1150d285c62b26659f62fb00824fceaffected · git
    • before 4.7not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.52-16.1.52-1
Debian:13linuxbefore 6.4.11-16.4.11-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2023-54187Dec 30, 2025 · f2fs: fix potential corruption when moving a directory
    31Monitor
  • ← EarlierCVE-2023-54188Dec 30, 2025 · dmaengine: apple-admac: Fix 'current_tx' not getting freed
    0Monitor
  • Later →CVE-2023-54239Dec 30, 2025 · iommufd: Check for uptr overflow
    0Monitor

Remediation

Which version to upgrade to

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

Product / packageFixed versionSource
Linux Linux1488d782c9e43087a3f341b8186cd25f3cf75583Vendor (CNA)
Linux Linux528c9d73153754defb748f0b96ad33308668d817Vendor (CNA)
Linux Linux813cede7b2f5a4b1b75d2d4bb4e705cc8e063b20Vendor (CNA)
Linux Linuxa3a3c7bddab9b6c5690b20796ef5e332b8c48afbVendor (CNA)
Linux Linuxa6d2fd1703cdc8ecfc3e73987e0fb7474ae2b074Vendor (CNA)
Linux Linuxb4f4ab423107dc1ba8e9cc6488c645be6403d3f5Vendor (CNA)
Linux Linuxcdcc35e6454133feb61561b4e0d0c80e52cbc2baVendor (CNA)
Linux Linuxdea499781a1150d285c62b26659f62fb00824fceVendor (CNA)
debian:linux6.1.52-1 · Debian:12Package 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.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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.

References

All records