{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89984 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89984 is a vulnerability in Linux, published on 16 Sep 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-89984 and fix it if it is affected.\n\nWhat it is: CVE-2026-89984 is a vulnerability in Linux, published on 16 Sep 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-89984 in the wild and no public exploit code.\n\nAffected product: Linux. 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-89984/ (Markdown: https://insights.sbomify.com/CVE-2026-89984/index.md)","id":"CVE-2026-89984","markdown":"https://insights.sbomify.com/CVE-2026-89984/index.md","name":"CVE-2026-89984","record":{"aliases":["AZL-101672","BELL-CVE-2026-89984","DEBIAN-CVE-2026-89984","GHSA-jjjc-8r8p-gw7x","UBUNTU-CVE-2026-89984"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"Local attackers can leak kernel memory addresses via Intel LBR stack filtering flaws, aiding privilege escalation or bypassing KASLR.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86/intel: Fix kernel address leakages in LBR stack\n\nBefore Arch LBR gained CPL filtering support, a user-only branch stack\ncould still contain kernel addresses. As a result, kernel branch records\nmay be exposed to user space even when PERF_SAMPLE_BRANCH_USER is\nrequested.\n\nFor example, on Intel Tiger Lake, the following command can still report\nSYSRET/ERET entries with kernel-space from addresses:\n\n$ ./perf record -e cycles:p -o - --branch-filter any,save_type,u -- \\\n \t./perf bench syscall basic --loop 1000 | \\\n\t./perf script -i - --fields brstack|tr ' ' '\\n'| \\\n\tgrep -E '0x[89a-f][0-9a-f]{15}'\n\n    Total time: 0.000 [sec]\n\n      0.219000 usecs/op\n     4,566,210 ops/sec\n[ perf record: Woken up 1 times to write data ]\n[ perf record: Captured and wrote 0.551 MB - ]\n0xffffffff93c001c8/0x7f12a2b1d647/P/-/-/16959/SYSRET/-\n0xffffffff93c001c8/0x7f12a2b1d5c2/P/-/-/17535/SYSRET/-\n0xffffffff93c01928/0x7f12a2861000/P/-/-/6719/ERET/-\n0xffffffff93c01928/0x7f12a297a000/P/-/-/8575/ERET/-\n\nThe problem is that intel_pmu_lbr_filter() does not fully validate the\nprivilege level of sampled entries. It filters some mismatches based on\nthe branch type and the to address, but it does not reject entries whose\nfrom address violates the requested branch privilege filter.\n\nFix this by extending software filtering to validate both from and to\naddresses against br_sel. Any LBR entry contains kernel address does not\nmatch the requested user filter is dropped. This prevents kernel\naddresses from appearing in user-only branch stacks.","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":"perf/x86/intel: Fix kernel address leakages in LBR stack","id":"CVE-2026-89984","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"memcg: keep folio's objcg same as its node","id":"CVE-2026-89985"},"packages":[],"prev":{"headline":"i2c: core: fix debugfs UAF on adapter removal","id":"CVE-2026-89983"},"products":["Linux"],"published":"2026-09-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"Local attackers can leak kernel memory addresses via Intel LBR stack filtering flaws, aiding privilege escalation or bypassing KASLR.","url":"https://insights.sbomify.com/CVE-2026-89984/"}