CVE-2026-99134 (GCVE-0-2026-99134)
Vulnerability from cvelistv5
Published
2026-10-28 10:34
Modified
2026-10-28 10:34
Severity ?
VLAI Severity ?
EPSS score ?
Summary
In the Linux kernel, the following vulnerability has been resolved:
mac802154: fix data race and NULL deref on local->assoc_dev
local->assoc_dev is shared between the association path and the
association-response worker without common synchronization.
mac802154_perform_association() stores the coordinator pointer and waits
for a response. Its timeout and error paths clear the pointer and return
to mac802154_associate(), which may then free the coordinator object.
Meanwhile, mac802154_rx_mac_cmd_worker() may observe the associating bit
and enter mac802154_process_association_resp(), which dereferences
assoc_dev.
The worker's bit test and the handler's pointer dereference are not
atomic with respect to cleanup. Cleanup can clear assoc_dev between them,
causing a NULL dereference, or free the coordinator while the response
handler still uses the pointer.
The recorded result is exposed to the same window. assoc_status and
assoc_addr are written by the handler but read by the association path
while the associating bit is still set, so a second response for the same
request - a malicious one, for instance - can replace them between those
reads and leave the caller with an incoherent status and address pair.
The response handler only needs the coordinator extended address.
Replace assoc_dev with a cached address, removing the pointer lifetime
dependency. Protect the cached address and the associating bit with a
dedicated spinlock. A READ_ONCE()/WRITE_ONCE() pair would not guarantee
an atomic __le64 access on all 32-bit architectures.
wpan_dev->association_lock cannot be reused here: nl802154_associate()
holds it across rdev_associate(), hence for the whole of
mac802154_perform_association() including the wait for the response.
A response handler taking that lock would only get it once the
association has already given up.
Reset the completion, publish the cached address, and set the associating
bit while holding the lock. The response handler takes the lock, rechecks
the bit and the cached address, records the response, clears the bit, and
only then completes the waiter. Thus cleanup cannot pass the handler
between its state check and completion, and the cached 64-bit value
cannot tear.
The handler clears the bit before completing, not the woken waiter:
otherwise complete() is issued under the lock and a second (e.g.
malicious) response can reacquire it before the waiter and replace the
result. So a wait that returns success implies the bit is already clear,
and the success and negative-response paths return directly. The
transmit-error and timeout paths still clear it under assoc_lock, which
serializes any racing response against the cleanup while the call returns
the error it already selected. Both paths snapshot assoc_status and
assoc_addr under the same lock.
Both users run in process context, so a plain spinlock is sufficient.
The lock is not held while waiting for the completion.
References
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"net/mac802154/ieee802154_i.h",
"net/mac802154/main.c",
"net/mac802154/scan.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "3cdd8b1abddebbae2582e90294c77b61d5f5aee7",
"status": "affected",
"version": "fefd19807fe9c65002366c749e809996a1ca4e68",
"versionType": "git"
},
{
"lessThan": "a585901bb8cd2cd60d678be8a56ca6a4e1a6946c",
"status": "affected",
"version": "fefd19807fe9c65002366c749e809996a1ca4e68",
"versionType": "git"
},
{
"lessThan": "c037915f80c4db47f7d061d68e703ffd551b1a34",
"status": "affected",
"version": "fefd19807fe9c65002366c749e809996a1ca4e68",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"net/mac802154/ieee802154_i.h",
"net/mac802154/main.c",
"net/mac802154/scan.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.8"
},
{
"lessThan": "6.8",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.59",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.13",
"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.59",
"versionStartIncluding": "6.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2.13",
"versionStartIncluding": "6.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3",
"versionStartIncluding": "6.8",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmac802154: fix data race and NULL deref on local-\u003eassoc_dev\n\nlocal-\u003eassoc_dev is shared between the association path and the\nassociation-response worker without common synchronization.\n\nmac802154_perform_association() stores the coordinator pointer and waits\nfor a response. Its timeout and error paths clear the pointer and return\nto mac802154_associate(), which may then free the coordinator object.\nMeanwhile, mac802154_rx_mac_cmd_worker() may observe the associating bit\nand enter mac802154_process_association_resp(), which dereferences\nassoc_dev.\n\nThe worker\u0027s bit test and the handler\u0027s pointer dereference are not\natomic with respect to cleanup. Cleanup can clear assoc_dev between them,\ncausing a NULL dereference, or free the coordinator while the response\nhandler still uses the pointer.\n\nThe recorded result is exposed to the same window. assoc_status and\nassoc_addr are written by the handler but read by the association path\nwhile the associating bit is still set, so a second response for the same\nrequest - a malicious one, for instance - can replace them between those\nreads and leave the caller with an incoherent status and address pair.\n\nThe response handler only needs the coordinator extended address.\nReplace assoc_dev with a cached address, removing the pointer lifetime\ndependency. Protect the cached address and the associating bit with a\ndedicated spinlock. A READ_ONCE()/WRITE_ONCE() pair would not guarantee\nan atomic __le64 access on all 32-bit architectures.\n\nwpan_dev-\u003eassociation_lock cannot be reused here: nl802154_associate()\nholds it across rdev_associate(), hence for the whole of\nmac802154_perform_association() including the wait for the response.\nA response handler taking that lock would only get it once the\nassociation has already given up.\n\nReset the completion, publish the cached address, and set the associating\nbit while holding the lock. The response handler takes the lock, rechecks\nthe bit and the cached address, records the response, clears the bit, and\nonly then completes the waiter. Thus cleanup cannot pass the handler\nbetween its state check and completion, and the cached 64-bit value\ncannot tear.\n\nThe handler clears the bit before completing, not the woken waiter:\notherwise complete() is issued under the lock and a second (e.g.\nmalicious) response can reacquire it before the waiter and replace the\nresult. So a wait that returns success implies the bit is already clear,\nand the success and negative-response paths return directly. The\ntransmit-error and timeout paths still clear it under assoc_lock, which\nserializes any racing response against the cleanup while the call returns\nthe error it already selected. Both paths snapshot assoc_status and\nassoc_addr under the same lock.\n\nBoth users run in process context, so a plain spinlock is sufficient.\nThe lock is not held while waiting for the completion."
}
],
"providerMetadata": {
"dateUpdated": "2026-10-28T10:34:47.193Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/3cdd8b1abddebbae2582e90294c77b61d5f5aee7"
},
{
"url": "https://git.kernel.org/stable/c/a585901bb8cd2cd60d678be8a56ca6a4e1a6946c"
},
{
"url": "https://git.kernel.org/stable/c/c037915f80c4db47f7d061d68e703ffd551b1a34"
}
],
"title": "mac802154: fix data race and NULL deref on local-\u003eassoc_dev",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-99134",
"datePublished": "2026-10-28T10:34:47.193Z",
"dateReserved": "2026-09-25T10:25:14.394Z",
"dateUpdated": "2026-10-28T10:34:47.193Z",
"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…