CVE-2026-63996
CVE CVE-2026-63996EUVD EUVD-2026-45569Published 2026-07-19T14:56:15.000ZLast changed 2026-08-05T12:38:00.000ZCVSS 7.8
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: ethtool: cmis: require exact CDB reply length Malicious SFP module could respond with rpl_len longer than what cmis_cdb_process_reply() expected, leading to OOB writes. Malicious HW is a bit theoretical but some modules may just be buggy and/or the reads may occasionally get corrupted, so let's protect the kernel. The existing check protects from short replies. We need to protect from long ones, too. All callers that pass a non-zero rpl_exp_len cast the reply payload to a fixed-layout struct and read fields at fixed offsets, with no version negotiation or short-reply handling: - cmis_cdb_validate_password() - cmis_cdb_module_features_get() - cmis_fw_update_fw_mng_features_get() so let's assume that responses longer than expected do not have to be handled gracefully here. Add a warning message to make the debug easier in case my understanding is wrong... Note that page_data->length (argument of kmalloc) comes from last arg to ethtool_cmis_page_init() which is rpl_exp_len. Note2 that AIs also like to point out overflows in args->req.payload itself (which is a fixed-size 120 B buffer, on the stack), but callers should be reading structs defined by the standard, so protecting from requests for more data than max seem like defensive programming.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux a39c84d796254e6b1662ca0c46dbc313379e9291 <eb5dcd740cd7fa27bc2caeff2d28ef28e93ff4d3; patch: 0; 6.11; a39c84d796254e6b1662ca0c46dbc313379e9291 <6c3f999a9d1338c6c89a9ff4549eafe72bc2e7b1; a39c84d796254e6b1662ca0c46dbc313379e9291 <2f818cc98fd2c63a08239cb48995f6c3bfe9d9b3; patch: 7.1; patch: 6.12.93; a39c84d796254e6b1662ca0c46dbc313379e9291 <4d42fb88ec61f2e98c33a9e3a2de371d5edbc6b1; patch: 6.18.35; patch: 7.0.12
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.