CVE-2023-53298
published 2025-09-16CVE-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…
PriorityP417medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.14%
3.4th percentile
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.
Affected
21 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.20-1 (bookworm) | linux 6.1.20-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 5ce3f32b5264b337bfd13a780452a17705307725 < 5321da6d84b87a34eea441677d649c34bd854169 | 5321da6d84b87a34eea441677d649c34bd854169 |
| linux | linux | >= 5ce3f32b5264b337bfd13a780452a17705307725 < af452e35b9e6a87cd49e54a7a3d60d934b194651 | af452e35b9e6a87cd49e54a7a3d60d934b194651 |
| linux | linux | >= 5ce3f32b5264b337bfd13a780452a17705307725 < 271eed1736426103335c5aac50f15b0f4d236bc0 | 271eed1736426103335c5aac50f15b0f4d236bc0 |
| linux | linux | >= 5ce3f32b5264b337bfd13a780452a17705307725 < 8978315cb4bf8878c9c8ec05dafd8f7ff539860d | 8978315cb4bf8878c9c8ec05dafd8f7ff539860d |
| linux | linux | >= 5ce3f32b5264b337bfd13a780452a17705307725 < c494365432dcdc549986f4d9af9eb6190cbdb153 | c494365432dcdc549986f4d9af9eb6190cbdb153 |
| linux | linux | >= 5ce3f32b5264b337bfd13a780452a17705307725 < b2036a252381949d3b743a3de069324ae3028a57 | b2036a252381949d3b743a3de069324ae3028a57 |
| linux | linux | >= 5ce3f32b5264b337bfd13a780452a17705307725 < ba98db08895748c12e5ded52cd1598dce2c79e55 | ba98db08895748c12e5ded52cd1598dce2c79e55 |
| linux | linux | >= 5ce3f32b5264b337bfd13a780452a17705307725 < 25ff6f8a5a3b8dc48e8abda6f013e8cc4b14ffea | 25ff6f8a5a3b8dc48e8abda6f013e8cc4b14ffea |
| linux | linux_kernel | >= 0 < 5.10.178-1 | 5.10.178-1 |
| linux | linux_kernel | >= 0 < 6.1.20-1 | 6.1.20-1 |
| linux | linux_kernel | >= 0 < 6.1.20-1 | 6.1.20-1 |
| linux | linux_kernel | >= 0 < 6.1.20-1 | 6.1.20-1 |
| linux | linux_kernel | >= 3.13 < 4.14.308 | 4.14.308 |
| linux | linux_kernel | >= 4.15 < 4.19.276 | 4.19.276 |
| linux | linux_kernel | >= 4.20 < 5.4.235 | 5.4.235 |
| linux | linux_kernel | >= 5.11 < 5.15.100 | 5.15.100 |
| linux | linux_kernel | >= 5.16 < 6.1.18 | 6.1.18 |
| linux | linux_kernel | >= 5.5 < 5.10.173 | 5.10.173 |
| linux | linux_kernel | >= 6.2 < 6.2.5 | 6.2.5 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: nfc: fix memory leak of se_io context in nfc_genl_se_io
vendor_redhat·2025-09-16·CVSS 5.5
CVE-2023-53298 [MEDIUM] kernel: nfc: fix memory leak of se_io context in nfc_genl_se_io
kernel: nfc: fix memory leak of se_io context in nfc_genl_se_io
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.
Package: kernel (Red Hat Enterprise Linux 10) - Not affected
Package: ker
Debian
CVE-2023-53298: linux - In the Linux kernel, the following vulnerability has been resolved: nfc: fix me...
vendor_debian·2023·CVSS 5.5
CVE-2023-53298 [MEDIUM] CVE-2023-53298: linux - In the Linux kernel, the following vulnerability has been resolved: nfc: fix me...
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.
Scope: local
bookworm: resolved (fixed in 6.1.20-1)
bullseye: resolved (fixed in 5.10.178-1)
forky: resolved (fixed in 6.1.20-1)
sid: resolv
GHSA
GHSA-jg3v-4f9w-62x2: 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
ghsa_unreviewed·2025-09-16
CVE-2023-53298 [MEDIUM] CWE-401 GHSA-jg3v-4f9w-62x2: 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
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.
OSV
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 s
osv·2025-09-16·CVSS 5.5
CVE-2023-53298 [MEDIUM] 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 s
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.
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/25ff6f8a5a3b8dc48e8abda6f013e8cc4b14ffeahttps://git.kernel.org/stable/c/271eed1736426103335c5aac50f15b0f4d236bc0https://git.kernel.org/stable/c/5321da6d84b87a34eea441677d649c34bd854169https://git.kernel.org/stable/c/8978315cb4bf8878c9c8ec05dafd8f7ff539860dhttps://git.kernel.org/stable/c/af452e35b9e6a87cd49e54a7a3d60d934b194651https://git.kernel.org/stable/c/b2036a252381949d3b743a3de069324ae3028a57https://git.kernel.org/stable/c/ba98db08895748c12e5ded52cd1598dce2c79e55https://git.kernel.org/stable/c/c494365432dcdc549986f4d9af9eb6190cbdb153
2025-09-16
Published