Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-50706

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

Not scoredEPSS 0.21%
Published
Updated
Reserved
Assigned by
Linux

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (7 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 8b68e53d56697a59b5c53893b53f508bbdf272a0 – < 4a36de8947794fa21435d1e916e089095f3246a8
    • affected 6204bf78b2a903b96ba43afff6abc0b04d6e0462 – < 791489a5c56396ddfed75fc525066d4738dace46
    • affected a75987714bd2d8e59840667a28e15c1fa5c47554 – < 34f31a2b667914ab701ca725554a0b447809d7ef
    • affected 72f2dc8993f10262092745a88cb2dd0fef094f23 – < df0da3fc131132b6c32a15c4da4ffa3a5aea1af2
    • affected fd1894224407c484f652ad456e1ce423e89bb3eb – < 9974d220c5073d035b5469d1d8ecd71da86c7afd
    • affected fd1894224407c484f652ad456e1ce423e89bb3eb – < b12e924a2f5b960373459c8f8a514f887adf5cac
    • affected 5.4.212 – < 5.4.220
    • affected 5.10.141 – < 5.10.150
    • affected 5.15.65 – < 5.15.75
    • affected 5.19.7 – < 5.19.17
  • Linux · Linux

    • affected 6.0
    • unaffected < 6.0
    • unaffected 5.4.220 – ≤ 5.4.*
    • unaffected 5.10.150 – ≤ 5.10.*
    • unaffected 5.15.75 – ≤ 5.15.*
    • unaffected 5.19.17 – ≤ 5.19.*
    • unaffected 6.0.3 – ≤ 6.0.*
    • unaffected 6.1 – ≤ *

References (6)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-50706 badge
[![CVE-2022-50706](https://trackcve.app/badge/CVE-2022-50706.svg)](https://trackcve.app/cve/CVE-2022-50706)

Record last updated .