Linux: Double Free
CVE-2023-53510 is a high-severity double free vulnerability in Linux, with a CVSS 3.1 base score of 7.8 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 b6d76d63c6d21d5d26c301a46853a2aee72397d5, f3ee24af62681b942bbd799ac77b90a6d7e1fdb1, 49234a401e161a2f2698f4612ab792c49b3cad1b 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.16% 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 b6d76d63c6d21d5d26c301a46853a2aee72397d5 or f3ee24af62681b942bbd799ac77b90a6d7e1fdb1 or 49234a401e161a2f2698f4612ab792c49b3cad1b or 549e91a9bbaa0ee480f59357868421a61d369770, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.1.167 or 6.3.13 or 6.4.4, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 5a0b0cb9bee767ef10ff9ce2fb4141af06416288 up to, but not including, b6d76d63c6d21d5d26c301a46853a2aee72397d5; 5a0b0cb9bee767ef10ff9ce2fb4141af06416288 up to, but not including, f3ee24af62681b942bbd799ac77b90a6d7e1fdb1; 5a0b0cb9bee767ef10ff9ce2fb4141af06416288 up to, but not including, 49234a401e161a2f2698f4612ab792c49b3cad1b; 5a0b0cb9bee767ef10ff9ce2fb4141af06416288 up to, but not including, 549e91a9bbaa0ee480f59357868421a61d369770; 3.12 | b6d76d63c6d21d5d26c301a46853a2aee72397d5, f3ee24af62681b942bbd799ac77b90a6d7e1fdb1, 49234a401e161a2f2698f4612ab792c49b3cad1b, 549e91a9bbaa0ee480f59357868421a61d369770 |
| Linux | Linux Kernel | 3.12 up to, but not including, 6.1.167; 6.2 up to, but not including, 6.3.13; 6.4 up to, but not including, 6.4.4 | 6.1.167, 6.3.13, 6.4.4 |
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
- HighData or code can be modified at will.
- 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:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.8 | High | CNA |
| CVSS 3.1 | 7.8 | High | NVD |
Official description
In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: core: Fix handling of lrbp->cmd ufshcd_queuecommand() may be called two times in a row for a SCSI command before it is completed. Hence make the following changes: - In the functions that submit a command, do not check the old value of lrbp->cmd nor clear lrbp->cmd in error paths. - In ufshcd_release_scsi_cmd(), do not clear lrbp->cmd. See also scsi_send_eh_cmnd(). This commit prevents that the following appears if a command times out: WARNING: at drivers/ufs/core/ufshcd.c:2965 ufshcd_queuecommand+0x6f8/0x9a8 Call trace: ufshcd_queuecommand+0x6f8/0x9a8 scsi_send_eh_cmnd+0x2c0/0x960 scsi_eh_test_devices+0x100/0x314 scsi_eh_ready_devs+0xd90/0x114c scsi_error_handler+0x2b4/0xb70 kthread+0x16c/0x1e0
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Double Free
The product calls free() twice on the same memory address.
How developers prevent this class of flaw
- Choose a language that provides automatic memory management.
- Ensure that each allocation is freed only once. After freeing a chunk, set the pointer to NULL to ensure the pointer cannot be freed again. In complicated error conditions, be sure that clean-up routines respect the state of allocation properly. If the language is object oriented, ensure that object destructors delete each chunk of memory only once.
- Use a static analysis tool to find double free instances.
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Recent Double Free vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.