Bug 2395668 (CVE-2023-53298) - CVE-2023-53298 kernel: nfc: fix memory leak of se_io context in nfc_genl_se_io
Summary: CVE-2023-53298 kernel: nfc: fix memory leak of se_io context in nfc_genl_se_io
Keywords:
Status: NEW
Alias: CVE-2023-53298
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-09-16 09:02 UTC by OSIDB Bzimport
Modified: 2025-11-26 09:27 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-09-16 09:02:19 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.