CVE-2023-53298nfc: fix memory leak of se_io context in nfc_genl_se_io
- 5.5MediumCVSS base score
- 0.16%Exploitation in 30 daysEPSS · top 95% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
Published
- 8 months later
· 8 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| CISA-ADPADP (enrichment) | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.16% · top 95% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 5ce3f32b5264b337bfd13a780452a17705307725 – < 5321da6d84b87a34eea441677d649c34bd854169
- affected 5ce3f32b5264b337bfd13a780452a17705307725 – < af452e35b9e6a87cd49e54a7a3d60d934b194651
- affected 5ce3f32b5264b337bfd13a780452a17705307725 – < 271eed1736426103335c5aac50f15b0f4d236bc0
- affected 5ce3f32b5264b337bfd13a780452a17705307725 – < 8978315cb4bf8878c9c8ec05dafd8f7ff539860d
- affected 5ce3f32b5264b337bfd13a780452a17705307725 – < c494365432dcdc549986f4d9af9eb6190cbdb153
- affected 5ce3f32b5264b337bfd13a780452a17705307725 – < b2036a252381949d3b743a3de069324ae3028a57
- affected 5ce3f32b5264b337bfd13a780452a17705307725 – < ba98db08895748c12e5ded52cd1598dce2c79e55
- affected 5ce3f32b5264b337bfd13a780452a17705307725 – < 25ff6f8a5a3b8dc48e8abda6f013e8cc4b14ffea
- affected 3.13
- unaffected < 3.13
- unaffected 4.14.308 – ≤ 4.14.*
- unaffected 4.19.276 – ≤ 4.19.*
- unaffected 5.4.235 – ≤ 5.4.*
- unaffected 5.10.173 – ≤ 5.10.*
- unaffected 5.15.100 – ≤ 5.15.*
- unaffected 6.1.18 – ≤ 6.1.*
- unaffected 6.2.5 – ≤ 6.2.*
- unaffected 6.3 – ≤ *
References
References8
- https://git.kernel.org/stable/c/5321da6d84b87a34eea441677d649c34bd854169 (opens in a new tab)
- https://git.kernel.org/stable/c/af452e35b9e6a87cd49e54a7a3d60d934b194651 (opens in a new tab)
- https://git.kernel.org/stable/c/271eed1736426103335c5aac50f15b0f4d236bc0 (opens in a new tab)
- https://git.kernel.org/stable/c/8978315cb4bf8878c9c8ec05dafd8f7ff539860d (opens in a new tab)
- https://git.kernel.org/stable/c/c494365432dcdc549986f4d9af9eb6190cbdb153 (opens in a new tab)
- https://git.kernel.org/stable/c/b2036a252381949d3b743a3de069324ae3028a57 (opens in a new tab)
- https://git.kernel.org/stable/c/ba98db08895748c12e5ded52cd1598dce2c79e55 (opens in a new tab)
- https://git.kernel.org/stable/c/25ff6f8a5a3b8dc48e8abda6f013e8cc4b14ffea (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2023-59891 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2023-53298)Record last updated .