CVE-2024-26777: fbdev: sis: Error out if pixclock equals zero
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- Upgrade to the fixed version for your release line, or later: 4.19.308; 5.4.270; 5.10.211; 5.15.150; 6.1.80; 6.6.19; 6.7.7; 6.8 CVE record
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
In the Linux kernel, the following vulnerability has been resolved: fbdev: sis: Error out if pixclock equals zero The userspace program could pass any values to the driver through ioctl() interface. If the driver doesn't check the value of pixclock, it may cause divide-by-zero error. In sisfb_check_var(), var->pixclock is used as a divisor to caculate drate before it is checked against zero. Fix this by checking it at the beginning. This is similar to CVE-2022-3061 in i740fb which was fixed by commit 15cf0b8.
- weakness
- Not named by the CNA. NVD maps it to CWE-369.
- affected
- Linux
- published ranges
- linux kernel < 4.19.308; linux kernel >= 4.20 < 5.4.270; linux kernel >= 5.5 < 5.10.211; linux kernel >= 5.11 < 5.15.150; and 5 more on the CVE page
- fixed in
- 4.19.308; 5.4.270; 5.10.211; 5.15.150; 6.1.80; 6.6.19; 6.7.7; 6.8
- fixed by package (from OSV advisories)
- Kernel (Linux): 4.19.308; 5.4.270; 5.15.150; 6.1.80; 5.10.211; 6.6.19; 6.7.7 CVE-2024-26777
- assigned by
- Linux
- published
- 2024-04-03
check us git.kernel.org git.kernel.org git.kernel.org git.kernel.org
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 4 Apr 2024 | 0.00044 | |
| 28 Feb 2025 | 0.00042 | |
| 17 Mar 2025 | 0.00086 | scoring model v2025.03.14 |
| 29 Mar 2025 | 0.00382 | |
| 30 Mar 2025 | 0.00086 | |
| 15 Apr 2025 | 0.00046 | |
| 12 May 2025 | 0.00009 | |
| 15 Jun 2025 | 0.00008 | |
| 22 Jun 2025 | 0.00007 | |
| 20 Aug 2025 | 0.00008 | |
| 2 Sep 2025 | 0.00007 | |
| 18 Nov 2025 | 0.00074 | |
| 21 Nov 2025 | 0.00007 | |
| 22 Nov 2025 | 0.00008 | |
| 5 Dec 2025 | 0.00007 | |
| 15 Jun 2026 | 0.00254 | scoring model v2026.06.15 |
16 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.00 on 2026-06-15 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- Held: 4.19.308; 5.4.270; 5.10.211; 5.15.150; 6.1.80; 6.6.19; 6.7.7; 6.8. A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2024-26777', '2026-11-01T23:59:59.999999Z', now());