GSD-2022-1000171
drm/nouveau: fix off by one in BIOS boundary checking
drm/nouveau: fix off by one in BIOS boundary checking
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven. This ID is fixed in Linux Kernel version v5.4.178 by commit acc887ba88333f5fec49631f12d8cc7ebd95781c, it was introduced in version v4.8 by commit 4d4e9907ff572bb1d1c0f6913ad6e3d6d4525077. For more details please see the references link.
What each source reports
OSV No score
drm/nouveau: fix off by one in BIOS boundary checking
drm/nouveau: fix off by one in BIOS boundary checking
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven. This ID is fixed in Linux Kernel version v5.4.178 by commit acc887ba88333f5fec49631f12d8cc7ebd95781c, it was introduced in version v4.8 by commit 4d4e9907ff572bb1d1c0f6913ad6e3d6d4525077. For more details please see the references link.
- Record
GSD-2022-1000171- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
KernelLinux |
Listed versions, plus commit ranges v4.10v4.10-rc1v4.10-rc2v4.10-rc3v4.10-rc4 Show 45 moreShow lessv4.10-rc5v4.10-rc6v4.10-rc7v4.10-rc8v4.11v4.11-rc1v4.11-rc2v4.11-rc3v4.11-rc4v4.11-rc5v4.11-rc6v4.11-rc7v4.11-rc8v4.12v4.12-rc1v4.12-rc2v4.12-rc3v4.12-rc4v4.12-rc5v4.12-rc6v4.12-rc7v4.13v4.13-rc1v4.13-rc2v4.13-rc3v4.13-rc4v4.13-rc5v4.13-rc6v4.13-rc7v4.14v4.14-rc1v4.14-rc2v4.14-rc3v4.14-rc4v4.14-rc5v4.14-rc6v4.14-rc7v4.14-rc8v4.15v4.15-rc1v4.15-rc2v4.15-rc3v4.15-rc4v4.15-rc5v4.15-rc6 |
None known |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
GSD-2022-1000171 is a vulnerability with no CVSS score yet in Kernel, published February 18, 2022. No source lists public exploit code. No source names a fixed version.
Left out here: 286 versions. The JSON record has them.