UBUNTU-CVE-2025-21903
In the Linux kernel, the following vulnerability has been resolved: mctp i3c: handle NULL header address daddr can be NULL if there is no neighbour table entry present, in that case the tx packet should be dropped. saddr will usually be set by MCTP core, but check for NULL in case a packet is transmitted by a different protocol.
02 / AFFECTED SOFTWARE
Affected packages
29 explicit affected versions
10 explicit affected versions
11 explicit affected versions
3 explicit affected versions
1 explicit affected versions
3 explicit affected versions
7 explicit affected versions
26 explicit affected versions
26 explicit affected versions
37 explicit affected versions
10 explicit affected versions
10 explicit affected versions
13 explicit affected versions
13 explicit affected versions
8 explicit affected versions
78 explicit affected versions
45 explicit affected versions
37 explicit affected versions
8 explicit affected versions
4 explicit affected versions
8 explicit affected versions
19 explicit affected versions
24 explicit affected versions
23 explicit affected versions
7 explicit affected versions
34 explicit affected versions
10 explicit affected versions
32 explicit affected versions
33 explicit affected versions
31 explicit affected versions
16 explicit affected versions
13 explicit affected versions
4 explicit affected versions
12 explicit affected versions
5 explicit affected versions
38 explicit affected versions
51 explicit affected versions
13 explicit affected versions
6 explicit affected versions
25 explicit affected versions
10 explicit affected versions
10 explicit affected versions
26 explicit affected versions
13 explicit affected versions
25 explicit affected versions
1 explicit affected versions
31 explicit affected versions
10 explicit affected versions
10 explicit affected versions
1 explicit affected versions
19 explicit affected versions
8 explicit affected versions
13 explicit affected versions
21 explicit affected versions
6 explicit affected versions
13 explicit affected versions
12 explicit affected versions
24 explicit affected versions
18 explicit affected versions
7 explicit affected versions
14 explicit affected versions
25 explicit affected versions
21 explicit affected versions
12 explicit affected versions
26 explicit affected versions
1 explicit affected versions
20 explicit affected versions
3 explicit affected versions
23 explicit affected versions
24 explicit affected versions
14 explicit affected versions
5 explicit affected versions
30 explicit affected versions
3 explicit affected versions
26 explicit affected versions
12 explicit affected versions
44 explicit affected versions
4 explicit affected versions
4 explicit affected versions
16 explicit affected versions
9 explicit affected versions
12 explicit affected versions
29 explicit affected versions
13 explicit affected versions
5 explicit affected versions
7 explicit affected versions
6 explicit affected versions
5 explicit affected versions
13 explicit affected versions
7 explicit affected versions
6 explicit affected versions
10 explicit affected versions
14 explicit affected versions
18 explicit affected versions
3 explicit affected versions
16 explicit affected versions
1 explicit affected versions
43 explicit affected versions
30 explicit affected versions
11 explicit affected versions
36 explicit affected versions
35 explicit affected versions
23 explicit affected versions
35 explicit affected versions
12 explicit affected versions
13 explicit affected versions
28 explicit affected versions
4 explicit affected versions
6 explicit affected versions
12 explicit affected versions
15 explicit affected versions
50 explicit affected versions
26 explicit affected versions
11 explicit affected versions
12 explicit affected versions
26 explicit affected versions
27 explicit affected versions
27 explicit affected versions
12 explicit affected versions
7 explicit affected versions
03 / CONNECTIONS
Connected vulnerabilities
04 / EVIDENCE
Source records
In the Linux kernel, the following vulnerability has been resolved: mctp i3c: handle NULL header address daddr can be NULL if there is no neighbour table entry present, in that case the tx packet should be dropped. saddr will usually be set by MCTP core, but check for NULL in case a packet is transmitted by a different protocol.
05 / REFERENCES
Further evidence
- https://git.kernel.org/linus/cf7ee25e70c6edfac4553d6b671e8b19db1d9573
- https://ubuntu.com/security/CVE-2025-21903
- https://ubuntu.com/security/notices/USN-7605-1
- https://ubuntu.com/security/notices/USN-7605-2
- https://ubuntu.com/security/notices/USN-7606-1
- https://ubuntu.com/security/notices/USN-7628-1
- https://ubuntu.com/security/notices/USN-7764-1
- https://ubuntu.com/security/notices/USN-7764-2
- https://ubuntu.com/security/notices/USN-7765-1
- https://ubuntu.com/security/notices/USN-7766-1
- https://ubuntu.com/security/notices/USN-7767-1
- https://ubuntu.com/security/notices/USN-7767-2
- https://ubuntu.com/security/notices/USN-7779-1
- https://ubuntu.com/security/notices/USN-7790-1
- https://ubuntu.com/security/notices/USN-7800-1
- https://ubuntu.com/security/notices/USN-7801-1
- https://ubuntu.com/security/notices/USN-7801-2
- https://ubuntu.com/security/notices/USN-7801-3
- https://ubuntu.com/security/notices/USN-7802-1
- https://ubuntu.com/security/notices/USN-7809-1
- https://www.cve.org/CVERecord?id=CVE-2025-21903