CVE-2021-47444

See a problem?
Please try reporting it to the source first.
Source
https://nvd.nist.gov/vuln/detail/CVE-2021-47444
Import Source
https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2021-47444.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2021-47444
Related
Published
2024-05-22T07:15:09Z
Modified
2024-09-11T04:41:11.066867Z
Summary
[none]
Details

In the Linux kernel, the following vulnerability has been resolved:

drm/edid: In connectorbadedid() cap numofext by num_blocks read

In commit e11f5bd8228f ("drm: Add support for DP 1.4 Compliance edid corruption test") the function connectorbadedid() started assuming that the memory for the EDID passed to it was big enough to hold edid[0x7e] + 1 blocks of data (1 extra for the base block). It completely ignored the fact that the function was passed num_blocks which indicated how much memory had been allocated for the EDID.

Let's fix this by adding a bounds check.

This is important for handling the case where there's an error in the first block of the EDID. In that case we will call connectorbadedid() without having re-allocated memory based on edid[0x7e].

References

Affected packages

Debian:11 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
5.10.84-1

Affected versions

5.*

5.10.46-4
5.10.46-5
5.10.70-1~bpo10+1
5.10.70-1

Ecosystem specific 

{
    "urgency": "not yet assigned"
}

Debian:12 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
5.14.16-1

Ecosystem specific 

{
    "urgency": "not yet assigned"
}

Debian:13 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
5.14.16-1

Ecosystem specific 

{
    "urgency": "not yet assigned"
}