Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-46272: coresight: tmc-etr: Fix race condition between sysfs and perf mode

Noroxi assessment

Priority: Monitor (action score 18/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.12% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Linux Linux 206b6f672613d08b33e951a744d0a1c6ac5ad8ad, 38a07194bbcddb18d77dad40ba9978d994c0b74c, 3e8cdf184646c28c5ea5fba754d24a3b29068739.

Low priority for now. Upgrade to Linux Linux 206b6f672613d08b33e951a744d0a1c6ac5ad8ad, 38a07194bbcddb18d77dad40ba9978d994c0b74c, 3e8cdf184646c28c5ea5fba754d24a3b29068739 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: tmc-etr: Fix race condition between sysfs and perf mode When trying to run perf and sysfs mode simultaneously, the WARN_ON() in tmc_etr_enable_hw() is triggered sometimes: WARNING: CPU: 42 PID: 3911571 at drivers/hwtracing/coresight/coresight-tmc-etr.c:1060 tmc_etr_enable_hw+0xc0/0xd8 [coresight_tmc] [..snip..] Call trace: tmc_etr_enable_hw+0xc0/0xd8 [coresight_tmc] (P) tmc_enable_etr_sink+0x11c/0x250 [coresight_tmc] (L) tmc_enable_etr_sink+0x11c/0x250 [coresight_tmc] coresight_enable_path+0x1c8/0x218 [coresight] coresight_enable_sysfs+0xa4/0x228 [coresight] enable_source_store+0x58/0xa8 [coresight] dev_attr_store+0x20/0x40 sysfs_kf_write+0x4c/0x68 kernfs_fop_write_iter+0x120/0x1b8 vfs_write+0x2c8/0x388 ksys_write+0x74/0x108 __arm64_sys_write+0x24/0x38 el0_svc_common.constprop.0+0x64/0x148 do_el0_svc+0x24/0x38 el0_svc+0x3c/0x130 el0t_64_sync_handler+0xc8/0xd0 el0t_64_sync+0x1ac/0x1b0 ---[ end trace 0000000000000000 ]--- Since the enablement of sysfs mode is separeted into two critical regions, one for sysfs buffer allocation and another for hardware enablement, it's possible to race with the perf mode. Fix this by double check whether the perf mode's been used before enabling the hardware in sysfs mode. mode: [sysfs mode] [perf mode] tmc_etr_get_sysfs_buffer() spin_lock(&drvdata->spinlock) [sysfs buffer allocation] spin_unlock(&drvdata->spinlock) spin_lock(&drvdata->spinlock) tmc_etr_enable_hw() drvdata->etr_buf = etr_perf->etr_buf spin_unlock(&drvdata->spinlock) spin_lock(&drvdata->spinlock) tmc_etr_enable_hw() WARN_ON(drvdata->etr_buf) // WARN sicne etr_buf initialized at the perf side spin_unlock(&drvdata->spinlock) With this fix, we retain the check for CS_MODE_PERF in get_etr_sysfs_buf. This ensures we verify whether the perf mode's already running before we actually allocate the buffer. Then we can save the time of allocating/freeing the sysfs buffer if race with the perf mode.

MediumCVSS 4.7 · v3.1—No exploit Fix available
Published
Jun 3, 2026
Updated
Oct 21, 2026
EPSS
0.1% · 1th percentile

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
18 / 40 · 4.7 / 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.

Follow CVE-2026-46272

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.

VendorProduct
linuxlinux kernel

Affected versions

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

  • linux linux kernel6.5 and later · before 6.18.14
  • linux linux kernel6.19 and later · before 6.19.4

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

    • 6.5affected
    • 296b01fd106e787d4463974a7f42d286a5df08cd and later · before 3e8cdf184646c28c5ea5fba754d24a3b29068739affected · git
    • 296b01fd106e787d4463974a7f42d286a5df08cd and later · before 206b6f672613d08b33e951a744d0a1c6ac5ad8adaffected · git
    • 296b01fd106e787d4463974a7f42d286a5df08cd and later · before 38a07194bbcddb18d77dad40ba9978d994c0b74caffected · git
    • 296b01fd106e787d4463974a7f42d286a5df08cd and later · before 6906aa70d4fc5900b954136e20e27c2be6d1acabaffected · git
    • 296b01fd106e787d4463974a7f42d286a5df08cd and later · before e6e43e82c79c97917cbe356c07e8a6f3f982ab53affected · git
    • before 6.5not 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
    • 6.18.14 and later · up to and including 6.18.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:13linuxbefore 6.12.115-26.12.115-2
Debian:14linuxbefore 6.18.14-16.18.14-1
openSUSE:Leap 16.0dtb-aarch64before 6.12.0-160000.39.16.12.0-160000.39.1
openSUSE:Leap 16.0kernel-64kbbefore 6.12.0-160000.39.16.12.0-160000.39.1
openSUSE:Leap 16.0kernel-azurebefore 6.12.0-160000.39.16.12.0-160000.39.1
openSUSE:Leap 16.0kernel-defaultbefore 6.12.0-160000.39.16.12.0-160000.39.1
openSUSE:Leap 16.0kernel-default-basebefore 6.12.0-160000.39.1.160000.2.256.12.0-160000.39.1.160000.2.25
openSUSE:Leap 16.0kernel-docsbefore 6.12.0-160000.39.16.12.0-160000.39.1
openSUSE:Leap 16.0kernel-kvmsmallbefore 6.12.0-160000.39.16.12.0-160000.39.1
openSUSE:Leap 16.0kernel-obs-buildbefore 6.12.0-160000.39.16.12.0-160000.39.1
openSUSE:Leap 16.0kernel-obs-qabefore 6.12.0-160000.39.16.12.0-160000.39.1
openSUSE:Leap 16.0kernel-rtbefore 6.12.0-160000.39.16.12.0-160000.39.1
openSUSE:Leap 16.0kernel-sourcebefore 6.12.0-160000.39.16.12.0-160000.39.1
openSUSE:Leap 16.0kernel-symsbefore 6.12.0-160000.39.16.12.0-160000.39.1
openSUSE:Leap 16.0kernel-zfcpdumpbefore 6.12.0-160000.39.16.12.0-160000.39.1
SUSE:Linux Enterprise Server 16.0kernel-azurebefore 6.12.0-160000.39.16.12.0-160000.39.1
SUSE:Linux Enterprise Server 16.0kernel-docsbefore 6.12.0-160000.39.16.12.0-160000.39.1
SUSE:Linux Enterprise Server 16.0kernel-kvmsmallbefore 6.12.0-160000.39.16.12.0-160000.39.1
SUSE:Linux Enterprise Server 16.0kernel-obs-qabefore 6.12.0-160000.39.16.12.0-160000.39.1
SUSE:Linux Enterprise Server 16.0kernel-zfcpdumpbefore 6.12.0-160000.39.16.12.0-160000.39.1
SUSE:Linux Micro 6.2kernel-64kbbefore 6.12.0-160000.39.16.12.0-160000.39.1
SUSE:Linux Micro 6.2kernel-defaultbefore 6.12.0-160000.39.16.12.0-160000.39.1
SUSE:Linux Micro 6.2kernel-default-basebefore 6.12.0-160000.39.1.160000.2.266.12.0-160000.39.1.160000.2.26
SUSE:Linux Micro 6.2kernel-rtbefore 6.12.0-160000.39.16.12.0-160000.39.1

+3

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-2026-46266Jun 3, 2026 · inet: RAW sockets using IPPROTO_RAW MUST drop incoming ICMP
    36Monitor
  • ← EarlierCVE-2026-46271Jun 3, 2026 · wifi: ath12k: do WoW offloads only on primary link
    31Monitor
  • Later →CVE-2026-46274Jun 8, 2026 · io-wq: check that the predecessor is hashed in io_wq_remove_pending()
    31Monitor

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 Linux206b6f672613d08b33e951a744d0a1c6ac5ad8adVendor (CNA)
Linux Linux38a07194bbcddb18d77dad40ba9978d994c0b74cVendor (CNA)
Linux Linux3e8cdf184646c28c5ea5fba754d24a3b29068739Vendor (CNA)
Linux Linux6906aa70d4fc5900b954136e20e27c2be6d1acabVendor (CNA)
Linux Linuxe6e43e82c79c97917cbe356c07e8a6f3f982ab53Vendor (CNA)
debian:linux6.12.115-2 · Debian:13Package registry (OSV)
debian:linux6.18.14-1 · Debian:14Package registry (OSV)
opensuse:dtb-aarch646.12.0-160000.39.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-64kb6.12.0-160000.39.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-azure6.12.0-160000.39.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-default6.12.0-160000.39.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-default-base6.12.0-160000.39.1.160000.2.25 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-docs6.12.0-160000.39.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-kvmsmall6.12.0-160000.39.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-obs-build6.12.0-160000.39.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-obs-qa6.12.0-160000.39.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-rt6.12.0-160000.39.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-source6.12.0-160000.39.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-syms6.12.0-160000.39.1 · openSUSE:Leap 16.0Package registry (OSV)
suse:kernel-64kb6.12.0-160000.39.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-azure6.12.0-160000.39.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-default6.12.0-160000.39.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-default-base6.12.0-160000.39.1.160000.2.26 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-docs6.12.0-160000.39.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-kvmsmall6.12.0-160000.39.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-obs-build6.12.0-160000.39.1 · SUSE:Linux Micro Extras 6.2Package registry (OSV)
suse:kernel-obs-qa6.12.0-160000.39.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-rt6.12.0-160000.39.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-source6.12.0-160000.39.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-syms6.12.0-160000.39.1 · SUSE:Linux Micro Extras 6.2Package registry (OSV)

+1

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.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/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.

ATT&CK techniques

—

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