CVE-2023-53298
Last modified
CVE-2023-53298 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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.. EPSS estimates a 0.14% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 3.13, < 4.14.308 |
| Linux | Linux Kernel | >= 4.15, < 4.19.276 |
| Linux | Linux Kernel | >= 4.20, < 5.4.235 |
| Linux | Linux Kernel | >= 5.5, < 5.10.173 |
| Linux | Linux Kernel | >= 5.11, < 5.15.100 |
| Linux | Linux Kernel | >= 5.16, < 6.1.18 |
| Linux | Linux Kernel | >= 6.2, < 6.2.5 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2023-53298?
How severe is CVE-2023-53298?
How do I fix CVE-2023-53298?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2023
- CVE-2023-53292In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53293Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2023-53294In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53295In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53296In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53297In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53299In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-5330Mattermost fails to enforce a limit for the size of the cach…7.5
- CVE-2023-53300In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53301In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2023-53302In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53303In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2023-53298?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
