{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98584 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98584 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-98584 and fix it if it is affected.\n\nWhat it is: CVE-2026-98584 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-98584 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-98584/ (Markdown: https://insights.sbomify.com/CVE-2026-98584/index.md)","id":"CVE-2026-98584","markdown":"https://insights.sbomify.com/CVE-2026-98584/index.md","name":"CVE-2026-98584","record":{"aliases":["BELL-CVE-2026-98584","DEBIAN-CVE-2026-98584","GHSA-r555-rgvq-cqv7","UBUNTU-CVE-2026-98584"],"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":"A local attacker can read uninitialized kernel stack memory via netlink filter dumps, potentially exposing sensitive data.","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\nnet/sched: fix potential stack infoleak in em_text_dump()\n\nem_text_dump() allocates struct tcf_em_text on the stack without zeroing\nit.  strscpy() writes the algorithm name and a NUL terminator into\nconf.algo[], leaving the remaining bytes uninitialised.  nla_put_nohdr()\nthen copies the full struct to the netlink response.\n\nKMSAN on Linux 7.2-rc6 reports two kernel-infoleak splats from this path,\none triggered via \"tc filter show\" and one via a raw RTM_GETTFILTER dump:\n\n  BUG: KMSAN: kernel-infoleak in _copy_to_iter+0x1c9/0x2620\n    nla_put_nohdr+0x83/0x130\n    em_text_dump+0x291/0x550\n  Local variable conf created at: em_text_dump+0x5d/0x550\n  Bytes 168-179 of 199 are uninitialized\n\nI am not certain whether this constitutes a real security problem in\npractice: the test was conducted in a controlled KMSAN environment and\nthe leaked stack bytes may or may not carry sensitive data on actual\nproduction kernels.  I am reporting it because KMSAN flagged it as a\nkernel-infoleak and the fix is straightforward.  I can provide a\nuserspace reproducer on request.\n\nThe original code used strncpy() which zero-pads to the destination size.\nCommit b04202d6065c (\"net/sched: replace strncpy with strscpy\") replaced\nit with strscpy(), which does not pad, creating this condition.\nZero-initialising the struct closes it.","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":"net/sched: fix potential stack infoleak in em_text_dump()","id":"CVE-2026-98584","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"eth: fbnic: Avoid rounding zero ring sizes","id":"CVE-2026-98585"},"packages":[],"prev":{"headline":"nfc: nfcmrvl: validate helper command length before pull","id":"CVE-2026-98583"},"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 local attacker can read uninitialized kernel stack memory via netlink filter dumps, potentially exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2026-98584/"}