In the Linux kernel, the following vulnerability has been resolved:
net: ieee802154: at86rf230: Stop leaking skb's
Upon error the ieee802154_xmit_complete() helper is not called. Only
ieee802154_wake_queue() is called manually. In the Tx case we then leak
the skb structure.
Free the skb structure upon error before returning when appropriate.
As the 'is_tx = 0' cannot be moved in the complete handler because of a
possible race between the delay in switching to STATE_RX_AACK_ON and a
new interrupt, we introduce an intermediate 'was_tx' boolean just for
this purpose.
There is no Fixes tag applying here, many changes have been made on this
area and the issue kind of always existed.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue is a memory leak in the at86rf230 IEEE 802.15.4 radio driver. When transmit errors occur, packet buffers may not be freed. Business risk is mainly for embedded, IoT, or industrial systems using this specific radio stack, where repeated errors could degrade availability.
Executive priority
Treat as targeted operational risk, not a broad enterprise emergency. Prioritize embedded, IoT, OT, or product fleets using Linux IEEE 802.15.4 radios, especially where availability matters and kernel patch cycles are slow.
Technical view
The vulnerable path is in the Linux ieee802154 at86rf230 driver. On some transmit error paths, ieee802154_xmit_complete() is not called and the skb is leaked. The upstream fix frees the skb when appropriate and adds a was_tx boolean to avoid a race around receive-state switching.
Likely exposure
Exposure is likely limited to Linux systems using the at86rf230 IEEE 802.15.4 driver or related hardware. General-purpose servers without this driver loaded are less likely to be affected. Exact exposure depends on kernel version, distro backports, and whether the radio interface is present and active.
Exploitation context
The provided sources do not report active exploitation, and KEV is false. No CVSS or CWE is included. The plausible impact from the source text is resource leakage on transmit error handling, which could affect availability in devices using this driver.
Researcher notes
Evidence is official but sparse. The source says no Fixes tag applies and the issue may have long existed. Affected-version data should be validated through distro backports. Do not assume remote exploitability from the available record alone.
Mitigation direction
Update to a kernel or vendor package containing the referenced stable fixes.
Check distribution advisories for backported fixes and exact package versions.
Disable or avoid loading the at86rf230 driver if the hardware is unused.
Reduce exposure of affected IEEE 802.15.4 interfaces where operationally possible.
Validation and detection
Inventory Linux kernels and devices using IEEE 802.15.4 at86rf230 hardware.
Confirm whether the at86rf230 module is built, loaded, or in use.
Map running kernels to vendor-fixed packages or referenced stable commits.
Review device logs for transmit errors, memory pressure, or radio instability.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-48794 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.