CVE-2023-53298
In the Linux kernel, the following vulnerability has been resolved: nfc: fix memory leak of se_io context in nfc_genl_se_io The callback context for sending/receiving APDUs to/from the selected secure element is allocated inside nfc_genl_se_io and…
Does this matter?
Lower severity and a low EPSS score (0.14%). Track it; it rarely justifies an emergency change on its own.
Description
In the Linux kernel, the following vulnerability has been resolved: nfc: fix memory leak of se_io context in nfc_genl_se_io The callback context for sending/receiving APDUs to/from the selected secure element is allocated inside nfc_genl_se_io and supposed to be eventually freed in se_io_cb callback function. However, there are several error paths where the bwi_timer is not charged to call se_io_cb later, and the cb_context is leaked. The patch proposes to free the cb_context explicitly on those error paths. At the moment we can't simply check 'dev->ops->se_io()' return value as it may be negative in both cases: when the timer was charged and was not.
- CVSS 3.1
- 5.5 MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- EPSS
- 0.14% probability · 4th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-401
- Affected
- linux/linux kernel
- Source
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
References
- https://git.kernel.org/stable/c/25ff6f8a5a3b8dc48e8abda6f013e8cc4b14ffeaPatch
- https://git.kernel.org/stable/c/271eed1736426103335c5aac50f15b0f4d236bc0Patch
- https://git.kernel.org/stable/c/5321da6d84b87a34eea441677d649c34bd854169Patch
- https://git.kernel.org/stable/c/8978315cb4bf8878c9c8ec05dafd8f7ff539860dPatch
- https://git.kernel.org/stable/c/af452e35b9e6a87cd49e54a7a3d60d934b194651Patch
- https://git.kernel.org/stable/c/b2036a252381949d3b743a3de069324ae3028a57Patch
- https://git.kernel.org/stable/c/ba98db08895748c12e5ded52cd1598dce2c79e55Patch
- https://git.kernel.org/stable/c/c494365432dcdc549986f4d9af9eb6190cbdb153Patch
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.