Linux: Use of Uninitialized Resource
CVE-2024-57911 is a high-severity use of uninitialized resource vulnerability in Linux, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 03fa47621bf8fcbf5994c5716021527853f9af3d, e1c1e8c05010103c9c9ea3e9c4304b0b7e2c8e4a, 006073761888a632c5d6f93e47c41760fa627f77 as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.26% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to 03fa47621bf8fcbf5994c5716021527853f9af3d or e1c1e8c05010103c9c9ea3e9c4304b0b7e2c8e4a or 006073761888a632c5d6f93e47c41760fa627f77 or b0642d9c871aea1f28eb02cd84d60434df594f67, whichever matches your release line, or a later version.
- Update Linux Kernel to 5.4.290 or 5.10.234 or 5.15.177 or 6.1.125, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 415f792447572ef1949a3cef5119bbce8cc66373 up to, but not including, 03fa47621bf8fcbf5994c5716021527853f9af3d; 415f792447572ef1949a3cef5119bbce8cc66373 up to, but not including, e1c1e8c05010103c9c9ea3e9c4304b0b7e2c8e4a; 415f792447572ef1949a3cef5119bbce8cc66373 up to, but not including, 006073761888a632c5d6f93e47c41760fa627f77; 415f792447572ef1949a3cef5119bbce8cc66373 up to, but not including, b0642d9c871aea1f28eb02cd84d60434df594f67; 415f792447572ef1949a3cef5119bbce8cc66373 up to, but not including, 74058395b2c63c8a438cf199d09094b640f8c7f4; 415f792447572ef1949a3cef5119bbce8cc66373 up to, but not including, ea703cda36da0dacb9a2fd876370003197d8a019; 415f792447572ef1949a3cef5119bbce8cc66373 up to, but not including, 333be433ee908a53f283beb95585dfc14c8ffb46; 4.5 | 03fa47621bf8fcbf5994c5716021527853f9af3d, e1c1e8c05010103c9c9ea3e9c4304b0b7e2c8e4a, 006073761888a632c5d6f93e47c41760fa627f77, b0642d9c871aea1f28eb02cd84d60434df594f67, 74058395b2c63c8a438cf199d09094b640f8c7f4, ea703cda36da0dacb9a2fd876370003197d8a019 |
| Linux | Linux Kernel | 4.5 up to, but not including, 5.4.290; 5.5 up to, but not including, 5.10.234; 5.11 up to, but not including, 5.15.177; 5.16 up to, but not including, 6.1.125; 6.2 up to, but not including, 6.6.72; 6.7 up to, but not including, 6.12.10; 6.13 | 5.4.290, 5.10.234, 5.15.177, 6.1.125, 6.6.72, 6.12.10 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.1 | High | NVD |
| CVSS 3.1 | 7.1 | High | CISA (ADP) |
Official description
In the Linux kernel, the following vulnerability has been resolved: iio: dummy: iio_simply_dummy_buffer: fix information leak in triggered buffer The 'data' array is allocated via kmalloc() and it is used to push data to user space from a triggered buffer, but it does not set values for inactive channels, as it only uses iio_for_each_active_channel() to assign new values. Use kzalloc for the memory allocation to avoid pushing uninitialized information to userspace.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of Uninitialized Resource
The product uses or accesses a resource that has not been initialized.
How developers prevent this class of flaw
- Explicitly initialize the resource before use. If this is performed through an API function or standard procedure, follow all required steps.
- Pay close attention to complex conditionals that affect initialization, since some branches might not perform the initialization.
- Avoid race conditions (CWE-362) during initialization routines.
More Use of Uninitialized Resource vulnerabilities (CWE-908)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- git.kernel.org/stable/c/006073761888a632c5d6f93e47c41760fa627f77
- git.kernel.org/stable/c/03fa47621bf8fcbf5994c5716021527853f9af3d
- git.kernel.org/stable/c/333be433ee908a53f283beb95585dfc14c8ffb46
- git.kernel.org/stable/c/74058395b2c63c8a438cf199d09094b640f8c7f4
- git.kernel.org/stable/c/b0642d9c871aea1f28eb02cd84d60434df594f67
- git.kernel.org/stable/c/e1c1e8c05010103c9c9ea3e9c4304b0b7e2c8e4a
- git.kernel.org/stable/c/ea703cda36da0dacb9a2fd876370003197d8a019
Other references
Recent Use of Uninitialized Resource vulnerabilities
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
Spotted an error? Tell us.