CVE-2026-98424 (GCVE-0-2026-98424)
Vulnerability from cvelistv5
Published
2026-10-14 13:27
Modified
2026-10-19 09:19
Severity ?
VLAI Severity ?
EPSS score ?
Summary
In the Linux kernel, the following vulnerability has been resolved:
wifi: cfg80211: undo netns switch if renaming the wiphy fails
Once all the interfaces have been moved, cfg80211_switch_netns()
moves the wiphy itself by setting its network namespace and then
renaming it, which makes sysfs move it. The rename can fail (but
only on allocation failures), leaving things mixed up and hitting
the warning there.
Ignoring it isn't great, undo the move and let the change fail
in this case. If undo fails then WARN, then things would again
be stuck in two different network namespaces.
References
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"net/wireless/core.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "96bef5667b0c4aecb1b850d2343f69b9d684abb9",
"status": "affected",
"version": "463d018323851a608eef52a9427b0585005c647f",
"versionType": "git"
},
{
"lessThan": "739b7bf3942da4cde8eedb143d01a16ed865d1d7",
"status": "affected",
"version": "463d018323851a608eef52a9427b0585005c647f",
"versionType": "git"
},
{
"lessThan": "a41bd1938a9bfe226d444172a7e20e4bd5097960",
"status": "affected",
"version": "463d018323851a608eef52a9427b0585005c647f",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"net/wireless/core.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "2.6.32"
},
{
"lessThan": "2.6.32",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.54",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.8",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.54",
"versionStartIncluding": "2.6.32",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2.8",
"versionStartIncluding": "2.6.32",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3",
"versionStartIncluding": "2.6.32",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: cfg80211: undo netns switch if renaming the wiphy fails\n\nOnce all the interfaces have been moved, cfg80211_switch_netns()\nmoves the wiphy itself by setting its network namespace and then\nrenaming it, which makes sysfs move it. The rename can fail (but\nonly on allocation failures), leaving things mixed up and hitting\nthe warning there.\n\nIgnoring it isn\u0027t great, undo the move and let the change fail\nin this case. If undo fails then WARN, then things would again\nbe stuck in two different network namespaces."
}
],
"providerMetadata": {
"dateUpdated": "2026-10-19T09:19:17.805Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/96bef5667b0c4aecb1b850d2343f69b9d684abb9"
},
{
"url": "https://git.kernel.org/stable/c/739b7bf3942da4cde8eedb143d01a16ed865d1d7"
},
{
"url": "https://git.kernel.org/stable/c/a41bd1938a9bfe226d444172a7e20e4bd5097960"
}
],
"title": "wifi: cfg80211: undo netns switch if renaming the wiphy fails",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-98424",
"datePublished": "2026-10-14T13:27:51.975Z",
"dateReserved": "2026-09-25T10:25:14.348Z",
"dateUpdated": "2026-10-19T09:19:17.805Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…