CVE-2022-50706

net/ieee802154: don't warn zero-sized raw_sendmsg()

N/A
Published: December 24, 2025 at 10:55 AM UTC
Updated: June 17, 2026 at 05:24 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.10.141 ≤ v < 5.10.1505.15.65 ≤ v < 5.15.755.19.7 ≤ v < 5.19.175.4.212 ≤ v < 5.4.2206.0 ≤ v < 6.0.36.0 ≤ v < 6.15.10.1415.15.655.19.75.4.2126.06204bf78b2a903b96ba43afff6abc0b04d6e046272f2dc8993f10262092745a88cb2dd0fef094f238b68e53d56697a59b5c53893b53f508bbdf272a0a75987714bd2d8e59840667a28e15c1fa5c47554fd1894224407c484f652ad456e1ce423e89bb3eb
Vendor states this is fixed in 34f31a2b667914ab701ca725554a0b447809d7ef (fixed)
Vendor states this is fixed in 4a36de8947794fa21435d1e916e089095f3246a8 (fixed)
Vendor states this is fixed in 791489a5c56396ddfed75fc525066d4738dace46 (fixed)
Vendor states this is fixed in 9974d220c5073d035b5469d1d8ecd71da86c7afd (fixed)
Vendor states this is fixed in b12e924a2f5b960373459c8f8a514f887adf5cac (fixed)
Vendor states this is fixed in df0da3fc131132b6c32a15c4da4ffa3a5aea1af2 (fixed)
Vendor states this is fixed in 5.10.150 (unaffected)
Vendor states this is fixed in 5.15.75 (unaffected)
Vendor states this is fixed in 5.19.17 (unaffected)
Vendor states this is fixed in 5.4.220 (unaffected)
Vendor states this is fixed in 6.0 (unaffected)
Vendor states this is fixed in 6.0.3 (unaffected)
Vendor states this is fixed in 6.1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card