{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98922 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-98922 is a vulnerability in Linux, published on 23 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-98922 and fix it if it is affected.\n\nWhat it is: CVE-2026-98922 is a vulnerability in Linux, published on 23 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-98922 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-98922/ (Markdown: https://insights.sbomify.com/CVE-2026-98922/index.md)","id":"CVE-2026-98922","markdown":"https://insights.sbomify.com/CVE-2026-98922/index.md","name":"CVE-2026-98922","record":{"aliases":["DEBIAN-CVE-2026-98922","GHSA-x8q8-qwc9-fpg3","UBUNTU-CVE-2026-98922"],"analysis":null,"analysis_generated_by":null,"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: emac: move setting of netops to fix crash\n\nfixes the following crash on driver initialization:\n\n|BUG: Kernel NULL pointer dereference on read at 0x00000158\n|Faulting instruction address: 0xc0566b40\n|Oops: Kernel access of bad area, sig: 11 [#1]\n|BE PAGE_SIZE=4K  PowerPC 44x Platform\n|Modules linked in:\n|CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Tainted: GW 7.3.0-rc3+ #1\n|Tainted: [W]=WARN\n|Hardware name: MyBook Live APM821XX 0x12c41c83 PowerPC 44x Platform\n|NIP:  c0566b40 LR: c05648f8 CTR: c04c1e9c\n|REGS: c1053a20 TRAP: 0300   Tainted: GW  (7.3.0-rc3+)\n|MSR:  0002b000 \u003cCE,EE,FP,ME\u003e  CR: 24008808  XER: 00000000\n|DEAR: 00000158 ESR: 00000000\n|GPR00: c05648f8 c1053b10 c1063600 c1030000 c5ab3000 00000000 [...]\n|GPR08: 00000002 00000000 00000000 c1053b40 84002808 00000000 [...]\n|GPR16: cfffd210 00000002 c0beafcc cfffc960 00000000 c1030644 [...]\n|GPR24: c0beafbc c1037000 00000000 0000000a 00000000 c1030000 [...]\n|NIP [c0566b40] phy_link_topo_add_phy+0x2c/0x1d0\n|LR [c05648f8] phy_attach_direct+0x1a4/0x368\n|Call Trace:\n|[c1053b10] [c0811e04] klist_put+0x54/0xb4 (unreliable)\n|[c1053b40] [c05648f8] phy_attach_direct+0x1a4/0x368\n|[c1053b70] [c0564ae8] phy_connect_direct+0x2c/0x60\n|[c1053b90] [c056c7a8] of_phy_connect+0x50/0x74\n|[c1053bc0] [c0572a88] emac_probe+0xd50/0x119c\n|[c1053c90] [c04cb770] platform_probe+0x74/0xa4\n|[c1053cb0] [c04c8f08] really_probe+0x120/0x2b0\n|[c1053cd0] [c04c9254] __driver_probe_device+0x1bc/0x1fc\n|[c1053d00] [c04c9334] driver_probe_device+0x38/0xa8\n|[c1053d30] [c04c9560] __driver_attach+0xf4/0x10c\n|[c1053d50] [c04c6af8] bus_for_each_dev+0x68/0xd0\n|[c1053d90] [c04c7c34] bus_add_driver+0xcc/0x1ec\n|[c1053dc0] [c04c9f6c] driver_register+0xcc/0x110\n|[c1053de0] [c0aa3f40] emac_init+0x1c4/0x200\n\nThis bug showed up starting with v7.3-rc1. At the NIP in\nphy_link_topo_add_phy() is a netdev_need_ops_lock() check.\nThis was added by the following\ncommit ded86da4bbb7 (\"net: ethtool: relax ethnl_req_get_phydev() locking assertion\")\n\nThe bug shows up because at the time of_phy_connect() was called, the\nnetdev_ops were *not yet* determined. My fix is to move the code that\nsets netdev_ops+commac.ops+ethtool_ops further up as emac_init_config()\nderives that by looking at the device-tree and sets the required\ndev-\u003ephy_mode accordingly.\n\nDuring review, the Sashiko bot's AI stated that the commac assignment\nbecame a dead store. Great catch! To keep the original behavior as-is,\none mentioned option \"set dev-\u003ecommac.ops = \u0026emac_commac_ops only in\nthe non-gige case?\" sounded like a great plan. So the dev-\u003ecommac.ops\nassignment for the non-gige-case moves into the else block.\n\nThis patch was tested on a WD MyBook Live (RGMII). the device now works again.","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: emac: move setting of netops to fix crash","id":"CVE-2026-98922","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"arm64: io: Reject non-user protection in ioremap_prot()","id":"CVE-2026-98923"},"packages":[],"prev":{"headline":"ovl: fix UAF in ovl_do_mkdir() debug print","id":"CVE-2026-98921"},"products":["Linux"],"published":"2026-10-23","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-23","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-98922/"}