{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98619 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98619 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-98619 and fix it if it is affected.\n\nWhat it is: CVE-2026-98619 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-98619 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-98619/ (Markdown: https://insights.sbomify.com/CVE-2026-98619/index.md)","id":"CVE-2026-98619","markdown":"https://insights.sbomify.com/CVE-2026-98619/index.md","name":"CVE-2026-98619","record":{"aliases":["DEBIAN-CVE-2026-98619","GHSA-j42x-6wfg-qvw7","UBUNTU-CVE-2026-98619"],"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 ethtool self-test allows local attackers to trigger a kernel warning or potential instability by bypassing required locking mechanisms.","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\nnet: ethtool: keep rtnl_lock for the ioctl self test\n\nAn offline self test that brings the interface down and back up with\nnetif_close() / netif_open() requires rtnl_lock for both. Since the\nethtool IOCTL path became rtnl-optional for ops-locked drivers, the\nETHTOOL_TEST ioctl runs holding only the netdev instance lock, so on an\nops-locked driver the self test now tears the device down without\nrtnl_lock.\n\nWith lockdep this reproduces deterministically on every offline self\ntest on such a driver; note the sole lock held is the instance lock, not\nrtnl:\n\n  WARNING: suspicious RCU usage\n  net/core/netpoll.c:207 suspicious rcu_dereference_protected() usage!\n  1 lock held by ethtool/107:\n   #0: (\u0026dev-\u003elock){+.+.}, at: dev_ethtool\n  Call Trace:\n   netpoll_poll_disable\n   __dev_close_many\n   netif_close_many\n   netif_close\n   fbnic_self_test\n   dev_ethtool_locked\n   dev_ethtool\n   dev_ioctl\n   sock_ioctl\n   __x64_sys_ioctl\n\nWithout lockdep the same condition trips ASSERT_RTNL() in\n__dev_close_many() / __dev_open(); that check only samples the global\nrtnl state, so it can be masked by a concurrent rtnl holder, but the\ndevice is still being reconfigured without the lock it requires.\n\nThe ethtool self_test is a legacy ioctl-only command, so an ETHTOOL_TEST\ncase is only needed on the ioctl path. Add an opt-in bit for drivers whose\nself test needs rtnl_lock and set it on the ops-locked drivers whose\noffline self test tears the interface down and up:\n\n  - fbnic (ops-locked via queue_mgmt_ops): fbnic_self_test() offline path\n    uses netif_close() / netif_open().\n  - bnxt (ops-locked via queue_mgmt_ops): bnxt_self_test() offline path\n    goes through bnxt_close_nic() / bnxt_half_open_nic() /\n    bnxt_half_close_nic() / bnxt_open_nic(), which close and reopen the\n    device.","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: ethtool: keep rtnl_lock for the ioctl self test","id":"CVE-2026-98619","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"net: ethernet: mtk_eth_soc: unregister net_devices in case of probe failure","id":"CVE-2026-98620"},"packages":[],"prev":{"headline":"eth: fbnic: Handle maximum standalone channels","id":"CVE-2026-98618"},"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 ethtool self-test allows local attackers to trigger a kernel warning or potential instability by bypassing required locking mechanisms.","url":"https://insights.sbomify.com/CVE-2026-98619/"}