FKIE_CVE-2026-98922
Vulnerability from fkie_nvd - Published: 2026-10-23 13:17 - Updated: 2026-10-23 13:17
Severity
Summary
In the Linux kernel, the following vulnerability has been resolved:
net: emac: move setting of netops to fix crash
fixes the following crash on driver initialization:
|BUG: Kernel NULL pointer dereference on read at 0x00000158
|Faulting instruction address: 0xc0566b40
|Oops: Kernel access of bad area, sig: 11 [#1]
|BE PAGE_SIZE=4K PowerPC 44x Platform
|Modules linked in:
|CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Tainted: GW 7.3.0-rc3+ #1
|Tainted: [W]=WARN
|Hardware name: MyBook Live APM821XX 0x12c41c83 PowerPC 44x Platform
|NIP: c0566b40 LR: c05648f8 CTR: c04c1e9c
|REGS: c1053a20 TRAP: 0300 Tainted: GW (7.3.0-rc3+)
|MSR: 0002b000 <CE,EE,FP,ME> CR: 24008808 XER: 00000000
|DEAR: 00000158 ESR: 00000000
|GPR00: c05648f8 c1053b10 c1063600 c1030000 c5ab3000 00000000 [...]
|GPR08: 00000002 00000000 00000000 c1053b40 84002808 00000000 [...]
|GPR16: cfffd210 00000002 c0beafcc cfffc960 00000000 c1030644 [...]
|GPR24: c0beafbc c1037000 00000000 0000000a 00000000 c1030000 [...]
|NIP [c0566b40] phy_link_topo_add_phy+0x2c/0x1d0
|LR [c05648f8] phy_attach_direct+0x1a4/0x368
|Call Trace:
|[c1053b10] [c0811e04] klist_put+0x54/0xb4 (unreliable)
|[c1053b40] [c05648f8] phy_attach_direct+0x1a4/0x368
|[c1053b70] [c0564ae8] phy_connect_direct+0x2c/0x60
|[c1053b90] [c056c7a8] of_phy_connect+0x50/0x74
|[c1053bc0] [c0572a88] emac_probe+0xd50/0x119c
|[c1053c90] [c04cb770] platform_probe+0x74/0xa4
|[c1053cb0] [c04c8f08] really_probe+0x120/0x2b0
|[c1053cd0] [c04c9254] __driver_probe_device+0x1bc/0x1fc
|[c1053d00] [c04c9334] driver_probe_device+0x38/0xa8
|[c1053d30] [c04c9560] __driver_attach+0xf4/0x10c
|[c1053d50] [c04c6af8] bus_for_each_dev+0x68/0xd0
|[c1053d90] [c04c7c34] bus_add_driver+0xcc/0x1ec
|[c1053dc0] [c04c9f6c] driver_register+0xcc/0x110
|[c1053de0] [c0aa3f40] emac_init+0x1c4/0x200
This bug showed up starting with v7.3-rc1. At the NIP in
phy_link_topo_add_phy() is a netdev_need_ops_lock() check.
This was added by the following
commit ded86da4bbb7 ("net: ethtool: relax ethnl_req_get_phydev() locking assertion")
The bug shows up because at the time of_phy_connect() was called, the
netdev_ops were *not yet* determined. My fix is to move the code that
sets netdev_ops+commac.ops+ethtool_ops further up as emac_init_config()
derives that by looking at the device-tree and sets the required
dev->phy_mode accordingly.
During review, the Sashiko bot's AI stated that the commac assignment
became a dead store. Great catch! To keep the original behavior as-is,
one mentioned option "set dev->commac.ops = &emac_commac_ops only in
the non-gige case?" sounded like a great plan. So the dev->commac.ops
assignment for the non-gige-case moves into the else block.
This patch was tested on a WD MyBook Live (RGMII). the device now works again.
References
Impacted products
| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/net/ethernet/ibm/emac/core.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "c664cca8f622e66bea6a94279ae2611f1d1c0c67",
"status": "affected",
"version": "ded86da4bbb78cad74cecc368fee3ae3a296e2ca",
"versionType": "git"
},
{
"lessThan": "7c9f391ec89cb621d7af375ace2eb9a6248e5b9d",
"status": "affected",
"version": "ded86da4bbb78cad74cecc368fee3ae3a296e2ca",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/net/ethernet/ibm/emac/core.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "7.2"
},
{
"lessThan": "7.2",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.9",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "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\u0027s 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."
}
],
"id": "CVE-2026-98922",
"lastModified": "2026-10-23T13:17:12.840",
"metrics": {},
"published": "2026-10-23T13:17:12.840",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/7c9f391ec89cb621d7af375ace2eb9a6248e5b9d"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/c664cca8f622e66bea6a94279ae2611f1d1c0c67"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…