CVE-2024-44967 json
drm/mgag200: Bind I2C lifetime to DRM device
published 2024-09-04 2 y ago modified 2026-08-05 3 mo ago also EUVD-2024-41169
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 12%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
drm/mgag200: Bind I2C lifetime to DRM device
Managed cleanup with devm_add_action_or_reset() will release the I2C adapter when the underlying Linux device goes away. But the connector still refers to it, so this cleanup leaves behind a stale pointer in struct drm_connector.ddc.
Bind the lifetime of the I2C adapter to the connector's lifetime by using DRM's managed release. When the DRM device goes away (after the Linux device) DRM will first clean up the connector and then clean up the I2C adapter.
Patch / fix
- Linux Linux 6.1.105, 6.6.46, 6.10.5, 6.11
- linux Debian 12 6.1.106-1
- linux Debian 14, Debian 13 6.10.6-1
debian advisories DEBIAN-CVE-2024-44967
- linux Ubuntu 24.04 LTS 6.8.0-50.51
- linux-aws Ubuntu 24.04 LTS 6.8.0-1020.22
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1019.21
- linux-gke Ubuntu 24.04 LTS 6.8.0-1015.19
- linux-ibm Ubuntu 24.04 LTS 6.8.0-1017.17
- linux-azure Ubuntu 24.04 LTS 6.8.0-1020.23
- linux-gkeop Ubuntu 24.04 LTS 6.8.0-1002.4
- linux-raspi Ubuntu 24.04 LTS 6.8.0-1016.18
ubuntu advisories UBUNTU-CVE-2024-44967
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-rt Linux Micro 6.0 6.4.0-11.1
- kernel-source-rt Linux Micro 6.0 6.4.0-11.1
- kernel-livepatch-MICRO-6-0-RT_Update_3 Linux Micro 6.0 1-1.2
- kernel-source Linux Micro 6.0 6.4.0-20.1
- kernel-default Linux Micro 6.0 6.4.0-20.1
- kernel-kvmsmall Linux Micro 6.0 6.4.0-20.1
- kernel-default-base Linux Micro 6.0 6.4.0-17.1.1.51
- kernel-livepatch-MICRO-6-0_Update_3 Linux Micro 6.0 1-1.2
suse advisories SUSE-SU-2025:20077-1SUSE-SU-2025:20073-1SUSE-SU-2024:3592-1SUSE-SU-2024:3587-1SUSE-SU-2024:3569-1SUSE-SU-2024:3564-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2024-44967 updated cvss 6.7
kernel: drm/mgag200: Bind I2C lifetime to DRM device
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +82 moreaffected: no fix planned “Will not fix”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/55a6916db77102765b22855d3a0add4751988b7c
patch
-
git.kernel.org
/stable/c/81d34df843620e902dd04aa9205c875833d61c17
patch
-
git.kernel.org
/stable/c/9d96b91e03cba9dfcb4ac370c93af4dbc47d5191
patch
-
git.kernel.org
/stable/c/eb1ae34e48a09b7a1179c579aed042b032e408f4
patch
- lists.debian.org /debian-lts-announce/2025/01/msg00001.html
Sources
- CVE List CVE-2024-44967
- NVD CVE-2024-44967
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.