CVE-2025-21922: linux Use of Uninitialized Resource
Vulnerability summary
CVE-2025-21922 is a medium (CVSS 5.5) Use of Uninitialized Resource vulnerability in linux. EPSS estimates a 0.23% chance of exploitation in the next 30 days, higher than 12.7% of scored vulnerabilities.
Advisory lineage
Upstream 0 · Downstream 62 · Related 59Timeline
- 01-04-2025PublishedVulnerability first disclosed.
- 11-05-2026Last modifiedVulnerability information updated.
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
CVSS metrics
4 scores · 4 sources · 1 version- OSV · UbuntuEcosystem advisory · calculated5.5MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- OSV · DebianEcosystem advisory · calculated5.5MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- NVDNIST5.5MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS trend
Probability
0.23%
Chance of exploitation in the next 30 days
Percentile
13%
Versus all other CVEs
30-day change
0.00 pp
From 0.23% on 19-09-2026
Known exploited
Compare KEV catalogsNot in any of the 3 tracked catalogs.
Public exploits
0 foundNo public exploits indexed.
Weaknesses
CWE · root causeAffected systems
Ubuntu137 products
- linuxAll versions (No fix recorded) | < 5.4.0-216.236 | < 5.15.0-140.150 | < 6.8.0-84.84
- linux-allwinner-5.19All versions (No fix recorded)
- linux-awsAll versions (No fix recorded) | < 5.4.0-1146.156 | < 5.15.0-1084.91 | < 6.8.0-1039.41
- linux-aws-5.0All versions (No fix recorded)
- linux-aws-5.11All versions (No fix recorded)
Linux2 products
- linux≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < d685096c8129c9a92689975193e268945fd21dbf | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 2f591cb158807bdcf424f66f1fbfa6e4e50f3757 | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 4e2191b0fd0c064d37b0db67396216f2d4787e0f | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 3de809a768464528762757e433cd50de35bcb3c1 | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 1eacd47636a9de5bee25d9d5962dc538a82d9f0b | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 8aa8a40c766b3945b40565a70349d5581458ff63 | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < c036f5f2680cbdabdbbace86baee3c83721634d6 | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 4c2d14c40a68678d885eab4008a0129646805bae | 2.6.12
- linux_kernel≥ 2.6.12, < 5.4.291 | ≥ 5.5, < 5.10.235 | ≥ 5.11, < 5.15.179 | ≥ 5.16, < 6.1.131 | ≥ 6.2, < 6.6.83 | ≥ 6.7, < 6.12.19 | ≥ 6.13, < 6.13.7 | 6.14:rc1 | 6.14:rc2 | 6.14:rc3 | 6.14:rc4 | 6.14:rc5
Debian1 product
- linux< 6.1.133-1 | < 6.12.19-1
3 vendors · 140 products