Answer in brief
CVE-2026-45930 records a Medium severity (CVSS 5.5) vulnerability in net: mctp: ensure our nlmsg responses are initialised. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-45930 records a Medium severity (CVSS 5.5) vulnerability in net: mctp: ensure our nlmsg responses are initialised. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=583be982d93479ea3d85091b0fd0b01201ede87d <b37da3ac099e145bcd3be82c745a8d335772e3af || >=583be982d93479ea3d85091b0fd0b01201ede87d <c4f840437e7641764de15f2de951ac8335d641f1 || >=583be982d93479ea3d85091b0fd0b01201ede87d <963537a26fd892f7e414a091f807b44aeee97a7d || >=583be982d93479ea3d85091b0fd0b01201ede87d <976612471a9e6ead6ceffc241e4d0a1aac90b36a || >=583be982d93479ea3d85091b0fd0b01201ede87d <54ed418de62a148a655262da682a050fa05f7924 || >=583be982d93479ea3d85091b0fd0b01201ede87d <6fb6a97c86abb8592158088afaea0eb464cf9de1 || >=583be982d93479ea3d85091b0fd0b01201ede87d <a6a9bc544b675d8b5180f2718ec985ad267b5cbf | b37da3ac099e145bcd3be82c745a8d335772e3af, c4f840437e7641764de15f2de951ac8335d641f1, 963537a26fd892f7e414a091f807b44aeee97a7d, 976612471a9e6ead6ceffc241e4d0a1aac90b36a, 54ed418de62a148a655262da682a050fa05f7924, 6fb6a97c86abb8592158088afaea0eb464cf9de1, a6a9bc544b675d8b5180f2718ec985ad267b5cbf |
| Linux/Linuxgeneric | 5.15 | Not reported |
Published upstream
May 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 19, 2026
In the Linux kernel, the following vulnerability has been resolved: net: mctp: ensure our nlmsg responses are initialised Syed Faraz Abrar (@farazsth98) from Zellic, and Pumpkin (@u1f383) from DEVCORE Research Team working with Trend Micro Zero Day Initiative report that a RTM_GETNEIGH will return uninitalised data in the pad bytes of the ndmsg data. Ensure we're initialising the netlink data to zero, in the link, addr and neigh response messages.
Quoted source text, attributed separately from HOL analysis.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=583be982d93479ea3d85091b0fd0b01201ede87d <b37da3ac099e145bcd3be82c745a8d335772e3af || >=583be982d93479ea3d85091b0fd0b01201ede87d <c4f840437e7641764de15f2de951ac8335d641f1 || >=583be982d93479ea3d85091b0fd0b01201ede87d <963537a26fd892f7e414a091f807b44aeee97a7d || >=583be982d93479ea3d85091b0fd0b01201ede87d <976612471a9e6ead6ceffc241e4d0a1aac90b36a || >=583be982d93479ea3d85091b0fd0b01201ede87d <54ed418de62a148a655262da682a050fa05f7924 || >=583be982d93479ea3d85091b0fd0b01201ede87d <6fb6a97c86abb8592158088afaea0eb464cf9de1 || >=583be982d93479ea3d85091b0fd0b01201ede87d <a6a9bc544b675d8b5180f2718ec985ad267b5cbf | b37da3ac099e145bcd3be82c745a8d335772e3af, c4f840437e7641764de15f2de951ac8335d641f1, 963537a26fd892f7e414a091f807b44aeee97a7d, 976612471a9e6ead6ceffc241e4d0a1aac90b36a, 54ed418de62a148a655262da682a050fa05f7924, 6fb6a97c86abb8592158088afaea0eb464cf9de1, a6a9bc544b675d8b5180f2718ec985ad267b5cbf |
| Linux/Linuxgeneric | 5.15 | Not reported |
Published upstream
May 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 19, 2026
In the Linux kernel, the following vulnerability has been resolved: net: mctp: ensure our nlmsg responses are initialised Syed Faraz Abrar (@farazsth98) from Zellic, and Pumpkin (@u1f383) from DEVCORE Research Team working with Trend Micro Zero Day Initiative report that a RTM_GETNEIGH will return uninitalised data in the pad bytes of the ndmsg data. Ensure we're initialising the netlink data to zero, in the link, addr and neigh response messages.
Quoted source text, attributed separately from HOL analysis.