{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90098 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90098 is a denial of service vulnerability in Linux, published on 17 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-90098 and fix it if it is affected.\n\nWhat it is: CVE-2026-90098 is a denial of service vulnerability in Linux, published on 17 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-90098 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-90098/ (Markdown: https://insights.sbomify.com/CVE-2026-90098/index.md)","id":"CVE-2026-90098","markdown":"https://insights.sbomify.com/CVE-2026-90098/index.md","name":"CVE-2026-90098","record":{"aliases":["AZL-102804","BELL-CVE-2026-90098","DEBIAN-CVE-2026-90098","GHSA-68f7-xq35-m8h9","UBUNTU-CVE-2026-90098"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A local attacker can trigger a kernel crash by causing the Sparx5 network driver to sleep while holding a lock, resulting in a denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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: sparx5: fix sleep in atomic context in MAC table access\n\nsparx5_set_rx_mode() runs with netif_addr_lock_bh held and iterates\ndev-\u003emc via __dev_mc_sync(), which per address calls sparx5_mc_sync() /\nsparx5_mc_unsync() -\u003e sparx5_mact_learn() / sparx5_mact_forget().  These\ntake sparx5-\u003elock, a mutex, and then poll the MAC access command\nregister with readx_poll_timeout(). A mutex may block, which is not\nallowed from atomic context.\n\nConvert the driver to the new .ndo_set_rx_mode_async callback introduced\nin commit 3554b4345d85 (\"net: introduce ndo_set_rx_mode_async and\nnetdev_rx_mode_work\"). The async callback is invoked from process\ncontext, so the mutex and sleeping completion poll can remain.\n\nObserved with CONFIG_PROVE_LOCKING, CONFIG_DEBUG_SPINLOCK,\nCONFIG_DEBUG_MUTEXES and CONFIG_DEBUG_ATOMIC_SLEEP enabled:\n\n  BUG: sleeping function called from invalid context at kernel/locking/mutex.c:591\n  in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 217, name: ip\n  preempt_count: 201, expected: 0\n  Call trace:\n   __might_resched+0x144/0x248\n   __might_sleep+0x48/0x7c\n   __mutex_lock+0x74/0x850\n   mutex_lock_nested+0x24/0x30\n   sparx5_mact_learn+0x78/0x100\n   sparx5_mc_sync+0x40/0x54\n   __hw_addr_sync_dev+0xc4/0x170\n   sparx5_set_rx_mode+0x4c/0x58\n   __dev_set_rx_mode+0x64/0xa4\n   __dev_open+0x1ec/0x26c","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: sparx5: fix sleep in atomic context in MAC table access","id":"CVE-2026-90098","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"net/sched: account classifier filter allocations to memcg","id":"CVE-2026-90099"},"packages":[],"prev":{"headline":"Drivers: hv: vmbus: Skip VMBus module cleanup for non-nested root partition","id":"CVE-2026-90097"},"products":["Linux"],"published":"2026-09-17","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 trigger a kernel crash by causing the Sparx5 network driver to sleep while holding a lock, resulting in a denial of service.","url":"https://insights.sbomify.com/CVE-2026-90098/"}