Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-68376: coresight: ETR: Fix ETR buffer use-after-free issue

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 35501ac3c7d40a7bb9568c2f89d6b56beaf9bed3, 4e83434247ff8005a0b9a1ee997864abf8f259ec, 5d5d130835b417c7bfd6c942f0149e34397d4463.

Low priority for now. Upgrade to Linux Linux 35501ac3c7d40a7bb9568c2f89d6b56beaf9bed3, 4e83434247ff8005a0b9a1ee997864abf8f259ec, 5d5d130835b417c7bfd6c942f0149e34397d4463 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: coresight: ETR: Fix ETR buffer use-after-free issue When ETR is enabled as CS_MODE_SYSFS, if the buffer size is changed and enabled again, currently sysfs_buf will point to the newly allocated memory(buf_new) and free the old memory(buf_old). But the etr_buf that is being used by the ETR remains pointed to buf_old, not updated to buf_new. In this case, it will result in a memory use-after-free issue. Fix this by checking ETR's mode before updating and releasing buf_old, if the mode is CS_MODE_SYSFS, then skip updating and releasing it.

—No exploit Fix available
Published
Dec 24, 2025
Updated
Oct 21, 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-2025-68376

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 instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack 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 (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

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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.

—

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

    • fdd3ceb0001da6768bede9779a0190a42e65c404, 6.6affected
    • bd2767ec3df2775bc336f441f9068a989ccb919d and later · before 5d5d130835b417c7bfd6c942f0149e34397d4463affected · git
    • bd2767ec3df2775bc336f441f9068a989ccb919d and later · before 4e83434247ff8005a0b9a1ee997864abf8f259ecaffected · git
    • bd2767ec3df2775bc336f441f9068a989ccb919d and later · before 70acbc9c77686b7a521af6d7a543dcd9c324cf07affected · git
    • bd2767ec3df2775bc336f441f9068a989ccb919d and later · before cda077a19f5c8d6ec61e5b97deca203d95e3a422affected · git
    • bd2767ec3df2775bc336f441f9068a989ccb919d and later · before 35501ac3c7d40a7bb9568c2f89d6b56beaf9bed3affected · git
    • 6.5.8 and later · before 6.6affected · semver
    • before 6.6not affected · semver
    • 6.6.160 and later · up to and including 6.6.*not affected · semver
    • 6.12.114 and later · up to and including 6.12.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:13linuxfrom 0—
Debian:14linuxbefore 6.17.13-16.17.13-1

Same product

linux: all records

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-2025-68374Dec 24, 2025 · md: fix rcu protection in md_wakeup_thread
    0Monitor
  • ← EarlierCVE-2025-68375Dec 24, 2025 · perf/x86: Fix NULL event access and potential PEBS record loss
    0Monitor
  • Later →CVE-2025-68377Dec 24, 2025 · ns: initialize ns_list_node for initial namespaces
    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 Linux35501ac3c7d40a7bb9568c2f89d6b56beaf9bed3Vendor (CNA)
Linux Linux4e83434247ff8005a0b9a1ee997864abf8f259ecVendor (CNA)
Linux Linux5d5d130835b417c7bfd6c942f0149e34397d4463Vendor (CNA)
Linux Linux6.6Vendor (CNA)
Linux Linux70acbc9c77686b7a521af6d7a543dcd9c324cf07Vendor (CNA)
Linux Linuxcda077a19f5c8d6ec61e5b97deca203d95e3a422Vendor (CNA)
debian:linux6.17.13-1 · Debian:14Package 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

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.

Change log

  1. Fix✗ → ✓

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

References

Show all references (4 more)

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

All records