{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98398 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98398 is an use after free vulnerability in Linux, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-98398 and fix it if it is affected.\n\nWhat it is: CVE-2026-98398 is an use after free vulnerability in Linux, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-98398 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-98398/ (Markdown: https://insights.sbomify.com/CVE-2026-98398/index.md)","id":"CVE-2026-98398","markdown":"https://insights.sbomify.com/CVE-2026-98398/index.md","name":"CVE-2026-98398","record":{"aliases":["AZL-108176","BELL-CVE-2026-98398","DEBIAN-CVE-2026-98398","GHSA-qfc6-3g3r-6rjj","UBUNTU-CVE-2026-98398"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A use-after-free vulnerability in the Linux kernel lockdep subsystem allows attackers to trigger a kernel warning or potential crash via network traffic.","user_interaction":"not_required","vuln_class":"use_after_free"},"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\nlocking/lockdep: Invalidate stale class_cache entries for zapped classes\n\nsyzbot reported a lockdep splat hitting DEBUG_LOCKS_WARN_ON(1) in\nhlock_class() due to an invalid class_idx:\n\n  WARNING: kernel/locking/lockdep.c:238 at __lock_acquire+0x382/0x2cf0 kernel/locking/lockdep.c:5203\n  Workqueue: wg-crypt-wg0 wg_packet_tx_worker\n  RIP: 0010:hlock_class kernel/locking/lockdep.c:238 [inline]\n  RIP: 0010:check_wait_context kernel/locking/lockdep.c:4870 [inline]\n  RIP: 0010:__lock_acquire+0x389/0x2cf0 kernel/locking/lockdep.c:5203\n  Call Trace:\n   \u003cIRQ\u003e\n   lock_acquire+0x106/0x350 kernel/locking/lockdep.c:5886\n   _raw_spin_lock+0x2e/0x40 kernel/locking/spinlock.c:173\n   tcp_tsq_handler+0x29/0x200 net/ipv4/tcp_output.c:1291\n   tcp_tsq_workfn+0x384/0x410 net/ipv4/tcp_output.c:1325\n   ...\n\nWhen a lock class is zapped (e.g. during module unload or key\nunregistration), zap_class() clears the class's bit in\nlock_classes_in_use and removes it from the class hash table.\nHowever, existing lockdep_map instances embedded in data structures\nmay still retain a pointer to the zapped class in their class_cache[]\narray.\n\nWhen __lock_acquire() subsequently runs on such a lock, it finds\nlock-\u003eclass_cache[subclass] != NULL, skipping register_lock_class()\nand assigning hlock-\u003eclass_idx to the index of the zapped class. When\ncheck_wait_context() or hlock_class() inspects the held_lock, it finds\n!test_bit(class_idx, lock_classes_in_use) and warns. Furthermore, if\nthe zapped slot is subsequently re-allocated to an unrelated lock key,\nthe stale class_cache entry would erroneously match the unrelated\nclass (ABA issue).\n\nAdd lock_class_cache_is_valid() to validate that the cached class is\nwithin lock_classes bounds, still allocated in lock_classes_in_use\n(using uninstrumented arch_test_bit() in __always_inline context so it\nis safe in noinstr contexts like match_held_lock()), and that\nclass-\u003ekey matches the expected subkey (taking lockdep_set_subclass()\noverrides into account). Also use READ_ONCE()/WRITE_ONCE() when\naccessing class_cache[].  If the entry is invalid or stale, fall back\nto register_lock_class() / look_up_lock_class().","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":"locking/lockdep: Invalidate stale class_cache entries for zapped classes","id":"CVE-2026-98398","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"s390/ipl: Fix NULL deref in dump_reipl without re-IPL parm block","id":"CVE-2026-98399"},"packages":[],"prev":{"headline":"platform/x86: x86-android-tablets: hold device reference for secondary fwnode teardown","id":"CVE-2026-98397"},"products":["Linux"],"published":"2026-10-14","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 use-after-free vulnerability in the Linux kernel lockdep subsystem allows attackers to trigger a kernel warning or potential crash via network traffic.","url":"https://insights.sbomify.com/CVE-2026-98398/"}