CVE-2022-49978fbdev: fb_pm2fb: Avoid potential divide by zero error
- 5.5MediumCVSS base score
- 0.26%Exploitation in 30 daysEPSS · top 82% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: fbdev: fb_pm2fb: Avoid potential divide by zero error In `do_fb_ioctl()` of fbmem.c, if cmd is FBIOPUT_VSCREENINFO, var will be copied from user, then go through `fb_set_var()` and `info->fbops->fb_check_var()` which could may be `pm2fb_check_var()`. Along the path, `var->pixclock` won't be modified. This function checks whether reciprocal of `var->pixclock` is too high. If `var->pixclock` is zero, there will be a divide by zero error. So, it is necessary to check whether denominator is zero to avoid crash. As this bug is found by Syzkaller, logs are listed below. divide error in pm2fb_check_var Call Trace: <TASK> fb_set_var+0x367/0xeb0 drivers/video/fbdev/core/fbmem.c:1015 do_fb_ioctl+0x234/0x670 drivers/video/fbdev/core/fbmem.c:1110 fb_ioctl+0xdd/0x130 drivers/video/fbdev/core/fbmem.c:1189
Timeline
ID reserved
By Linux
Published
- 11 months later
· 11 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.26% · top 82% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 0f1174f4972ea9fad6becf8881d71adca8e9ca91
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 3ec326a6a0d4667585ca595f438c7293e5ced7c4
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 7f88cdfea8d7f4dbaf423d808241403b2bb945e4
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 7d9591b32a9092fc6391a316b56e8016c6181c3d
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 8fc778ee2fb2853f7a3531fa7273349640d8e4e9
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 34c3dea1189525cd533071ed5c176fc4ea8d982b
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < cb4bb011a683532841344ca7f281b5e04389b4f8
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 19f953e7435644b81332dd632ba1b2d80b1e37af
- affected 2.6.12
- unaffected < 2.6.12
- unaffected 4.9.327 – ≤ 4.9.*
- unaffected 4.14.292 – ≤ 4.14.*
- unaffected 4.19.257 – ≤ 4.19.*
- unaffected 5.4.212 – ≤ 5.4.*
- unaffected 5.10.141 – ≤ 5.10.*
- unaffected 5.15.65 – ≤ 5.15.*
- unaffected 5.19.7 – ≤ 5.19.*
- unaffected 6.0 – ≤ *
References
References8
- https://git.kernel.org/stable/c/0f1174f4972ea9fad6becf8881d71adca8e9ca91 (opens in a new tab)
- https://git.kernel.org/stable/c/3ec326a6a0d4667585ca595f438c7293e5ced7c4 (opens in a new tab)
- https://git.kernel.org/stable/c/7f88cdfea8d7f4dbaf423d808241403b2bb945e4 (opens in a new tab)
- https://git.kernel.org/stable/c/7d9591b32a9092fc6391a316b56e8016c6181c3d (opens in a new tab)
- https://git.kernel.org/stable/c/8fc778ee2fb2853f7a3531fa7273349640d8e4e9 (opens in a new tab)
- https://git.kernel.org/stable/c/34c3dea1189525cd533071ed5c176fc4ea8d982b (opens in a new tab)
- https://git.kernel.org/stable/c/cb4bb011a683532841344ca7f281b5e04389b4f8 (opens in a new tab)
- https://git.kernel.org/stable/c/19f953e7435644b81332dd632ba1b2d80b1e37af (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2022-55258 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2022-49978)Record last updated .