{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-46272 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-46272 is a medium-severity vulnerability in Linux kernel, published on 3 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-46272 and fix it if it is affected.\n\nWhat it is: CVE-2026-46272 is a medium-severity vulnerability in Linux kernel, published on 3 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-46272 in the wild and no public exploit code.\n\nAffected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-46272/ (Markdown: https://insights.sbomify.com/CVE-2026-46272/index.md)","id":"CVE-2026-46272","markdown":"https://insights.sbomify.com/CVE-2026-46272/index.md","name":"CVE-2026-46272","record":{"aliases":["BELL-CVE-2026-46272","DEBIAN-CVE-2026-46272","GHSA-v558-wf7v-xc9h","ROOT-OS-DEBIAN-13-CVE-2026-46272","ROOT-OS-UBUNTU-2404-CVE-2026-46272","UBUNTU-CVE-2026-46272"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel Coresight TMC ETR driver can trigger a kernel warning and potential instability when sysfs and perf modes are used simultaneously.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":4.7,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ncoresight: tmc-etr: Fix race condition between sysfs and perf mode\n\nWhen trying to run perf and sysfs mode simultaneously, the WARN_ON()\nin tmc_etr_enable_hw() is triggered sometimes:\n\n WARNING: CPU: 42 PID: 3911571 at drivers/hwtracing/coresight/coresight-tmc-etr.c:1060 tmc_etr_enable_hw+0xc0/0xd8 [coresight_tmc]\n [..snip..]\n Call trace:\n  tmc_etr_enable_hw+0xc0/0xd8 [coresight_tmc] (P)\n  tmc_enable_etr_sink+0x11c/0x250 [coresight_tmc] (L)\n  tmc_enable_etr_sink+0x11c/0x250 [coresight_tmc]\n  coresight_enable_path+0x1c8/0x218 [coresight]\n  coresight_enable_sysfs+0xa4/0x228 [coresight]\n  enable_source_store+0x58/0xa8 [coresight]\n  dev_attr_store+0x20/0x40\n  sysfs_kf_write+0x4c/0x68\n  kernfs_fop_write_iter+0x120/0x1b8\n  vfs_write+0x2c8/0x388\n  ksys_write+0x74/0x108\n  __arm64_sys_write+0x24/0x38\n  el0_svc_common.constprop.0+0x64/0x148\n  do_el0_svc+0x24/0x38\n  el0_svc+0x3c/0x130\n  el0t_64_sync_handler+0xc8/0xd0\n  el0t_64_sync+0x1ac/0x1b0\n ---[ end trace 0000000000000000 ]---\n\nSince the enablement of sysfs mode is separeted into two critical regions,\none for sysfs buffer allocation and another for hardware enablement, it's\npossible to race with the perf mode. Fix this by double check whether\nthe perf mode's been used before enabling the hardware in sysfs mode.\n\n mode:\n   [sysfs mode]                   [perf mode]\n   tmc_etr_get_sysfs_buffer()\n     spin_lock(\u0026drvdata-\u003espinlock)\n     [sysfs buffer allocation]\n     spin_unlock(\u0026drvdata-\u003espinlock)\n                                  spin_lock(\u0026drvdata-\u003espinlock)\n                                  tmc_etr_enable_hw()\n                                    drvdata-\u003eetr_buf = etr_perf-\u003eetr_buf\n                                  spin_unlock(\u0026drvdata-\u003espinlock)\n   spin_lock(\u0026drvdata-\u003espinlock)\n   tmc_etr_enable_hw()\n     WARN_ON(drvdata-\u003eetr_buf) // WARN sicne etr_buf initialized at\n                                  the perf side\n   spin_unlock(\u0026drvdata-\u003espinlock)\n\nWith this fix, we retain the check for CS_MODE_PERF in get_etr_sysfs_buf.\nThis ensures we verify whether the perf mode's already running before we\nactually allocate the buffer. Then we can save the time of\nallocating/freeing the sysfs buffer if race with the perf mode.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"coresight: tmc-etr: Fix race condition between sysfs and perf mode","id":"CVE-2026-46272","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"ibmveth: Disable GSO for packets with small MSS","id":"CVE-2026-46273"},"packages":[],"prev":{"headline":"wifi: ath12k: do WoW offloads only on primary link","id":"CVE-2026-46271"},"products":["Linux"],"published":"2026-06-03","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Linux"]},"summary":"A race condition in the Linux kernel Coresight TMC ETR driver can trigger a kernel warning and potential instability when sysfs and perf modes are used simultaneously.","url":"https://insights.sbomify.com/CVE-2026-46272/"}