In the Linux kernel, the following vulnerability has been resolved:
net/ieee802154: don't warn zero-sized raw_sendmsg()
syzbot is hitting skb_assert_len() warning at __dev_queue_xmit() [1],
for PF_IEEE802154 socket's zero-sized raw_sendmsg() request is hitting
__dev_queue_xmit() with skb->len == 0.
Since PF_IEEE802154 socket's zero-sized raw_sendmsg() request was
able to return 0, don't call __dev_queue_xmit() if packet length is 0.
----------
#include <sys/socket.h>
#include <netinet/in.h>
int main(int argc, char *argv[])
{
struct sockaddr_in addr = { .sin_family = AF_INET, .sin_addr.s_addr = htonl(INADDR_LOOPBACK) };
struct iovec iov = { };
struct msghdr hdr = { .msg_name = &addr, .msg_namelen = sizeof(addr), .msg_iov = &iov, .msg_iovlen = 1 };
sendmsg(socket(PF_IEEE802154, SOCK_RAW, 0), &hdr, 0);
return 0;
}
----------
Note that this might be a sign that commit fd1894224407c484 ("bpf: Don't
redirect packets with invalid pkt_len") should be reverted, for
skb->len == 0 was acceptable for at least PF_IEEE802154 socket.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue concerns an unusual zero-length send operation on IEEE 802.15.4 raw sockets. The kernel could reach a warning path instead of ignoring the empty packet. The public record does not provide CVSS, demonstrated impact beyond the warning, or evidence of active exploitation.
Executive priority
Treat as a routine kernel maintenance item unless your environment depends on IEEE 802.15.4 socket support. There is no source-backed evidence of active exploitation or severe impact in the supplied bundle.
Technical view
A zero-sized raw_sendmsg request for PF_IEEE802154 could call __dev_queue_xmit with skb->len equal to 0, triggering skb_assert_len warning behavior. The resolved change avoids calling transmit when packet length is zero. The record lists affected Linux kernel versions and stable kernel commits as references.
Likely exposure
Exposure is likely limited to Linux systems running affected kernel builds where PF_IEEE802154 raw sockets are present and usable. The source bundle does not establish remote exposure, privilege requirements, or a broader cross-product impact.
Exploitation context
CISA KEV is false in the bundle, and no cited source states active exploitation. The report originated from syzbot-style kernel testing. The included evidence shows a local socket behavior pattern, not a weaponized exploit campaign.
Researcher notes
The public evidence is narrow: zero-length PF_IEEE802154 raw_sendmsg reaches transmit with skb->len zero. Impact is described as a warning path, and the bundle does not provide CVSS, CWE, privilege assumptions, or confirmed security consequences beyond the resolved kernel behavior.
Mitigation direction
Update to a vendor-supported kernel containing the referenced stable fix.
Check Linux distribution advisories for backported package versions.
Prioritize systems exposing PF_IEEE802154 raw socket functionality.
Track the CVE record for severity or impact updates.
Validation and detection
Inventory Linux kernel versions against the affected versions in the CVE record.
Confirm installed kernels include one of the referenced stable fixes or vendor backports.
Check whether PF_IEEE802154 raw sockets are available on relevant systems.
Review kernel logs for related warning patterns if exposure is suspected.
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-50706 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.
0CVSS vectors
3Timeline events
0ADP providers
7Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Dec 24, 2025, 10:55 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.