{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98552 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98552 is a vulnerability in Linux, published on 18 Oct 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-98552 and fix it if it is affected.\n\nWhat it is: CVE-2026-98552 is a vulnerability in Linux, published on 18 Oct 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-98552 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-98552/ (Markdown: https://insights.sbomify.com/CVE-2026-98552/index.md)","id":"CVE-2026-98552","markdown":"https://insights.sbomify.com/CVE-2026-98552/index.md","name":"CVE-2026-98552","record":{"aliases":["BELL-CVE-2026-98552","DEBIAN-CVE-2026-98552","GHSA-x3q4-wwr6-jh85","UBUNTU-CVE-2026-98552"],"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's perf subsystem can cause a reference count leak, potentially leading to resource exhaustion and denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"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/core: Fix a refcount leak in attach_perf_ctx_data()\n\nThe attach_perf_ctx_data() can race on global and !global cases.  The\nglobal case is protected by global_ctx_data_rwsem and shares a single\nreference count using perf_ctx_data.global field.\n\nBut when it races with !global case, it may miss to set the global field\nand result in a reference count leak.\n\n CPU1                                  CPU2\n ----------------------------------------------------------------\n attach_task_ctx_data(.global=1)       attach_task_ctx_data(.global=0)\n   cd1 = alloc_perf_ctx_data();          cd2 = alloc_perf_ctx_data();\n                                         //    { .global = 0, .refcount = 1 };\n\n                                         try_cmpxchg(); // success,\n                                         // task-\u003eperf_ctx_data = cd2\n   try_cmpxhg(); // fail; old = cd2\n   refcount_inc_not_zero(\u0026old-\u003erefcount); // success\n     // old.refcount = 2\n   free_perf_ctx_data(cd1);\n\nThen later detach_global_ctx_data() will see the data but it's not\nmarked as global, so it won't call detach_task_ctx_data().","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/core: Fix a refcount leak in attach_perf_ctx_data()","id":"CVE-2026-98552","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"autofs: fix sbi-\u003epipe file reference leak in autofs_kill_sb()","id":"CVE-2026-98553"},"packages":[],"prev":{"headline":"perf/core: Fill branch entries with a single assignment","id":"CVE-2026-98551"},"products":["Linux"],"published":"2026-10-18","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":"A race condition in the Linux kernel's perf subsystem can cause a reference count leak, potentially leading to resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2026-98552/"}