Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-21922ppp: Fix KMSAN uninit-value warning with bpf

Description

In the Linux kernel, the following vulnerability has been resolved: ppp: Fix KMSAN uninit-value warning with bpf Syzbot caught an "KMSAN: uninit-value" warning [1], which is caused by the ppp driver not initializing a 2-byte header when using socket filter. The following code can generate a PPP filter BPF program: ''' struct bpf_program fp; pcap_t *handle; handle = pcap_open_dead(DLT_PPP_PPPD, 65535); pcap_compile(handle, &fp, "ip and outbound", 0, 0); bpf_dump(&fp, 1); ''' Its output is: ''' (000) ldh [2] (001) jeq #0x21 jt 2 jf 5 (002) ldb [0] (003) jeq #0x1 jt 4 jf 5 (004) ret #65535 (005) ret #0 ''' Wen can find similar code at the following link: https://github.com/ppp-project/ppp/blob/master/pppd/options.c#L1680 The maintainer of this code repository is also the original maintainer of the ppp driver. As you can see the BPF program skips 2 bytes of data and then reads the 'Protocol' field to determine if it's an IP packet. Then it read the first byte of the first 2 bytes to determine the direction. The issue is that only the first byte indicating direction is initialized in current ppp driver code while the second byte is not initialized. For normal BPF programs generated by libpcap, uninitialized data won't be used, so it's not a problem. However, for carefully crafted BPF programs, such as those generated by syzkaller [2], which start reading from offset 0, the uninitialized data will be used and caught by KMSAN. [1] https://syzkaller.appspot.com/bug?extid=853242d9c9917165d791 [2] https://syzkaller.appspot.com/text?tag=ReproC&x=11994913980000

Timeline

  1. ID reserved

    By Linux

  2. · 3 months later

    Published

  3. · 14 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

CVSS scores of CVE-2025-21922, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < d685096c8129c9a92689975193e268945fd21dbf
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 2f591cb158807bdcf424f66f1fbfa6e4e50f3757
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 4e2191b0fd0c064d37b0db67396216f2d4787e0f
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 3de809a768464528762757e433cd50de35bcb3c1
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 1eacd47636a9de5bee25d9d5962dc538a82d9f0b
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 8aa8a40c766b3945b40565a70349d5581458ff63
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < c036f5f2680cbdabdbbace86baee3c83721634d6
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 4c2d14c40a68678d885eab4008a0129646805bae
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.4.291 – ≤ 5.4.*
    • unaffected 5.10.235 – ≤ 5.10.*
    • unaffected 5.15.179 – ≤ 5.15.*
    • unaffected 6.1.131 – ≤ 6.1.*
    • unaffected 6.6.83 – ≤ 6.6.*
    • unaffected 6.12.19 – ≤ 6.12.*
    • unaffected 6.13.7 – ≤ 6.13.*
    • unaffected 6.14 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

CVE-2025-21922 badge
[![CVE-2025-21922](https://cveledger.app/badge/CVE-2025-21922.svg)](https://cveledger.app/cve/CVE-2025-21922)

Record last updated .