Bug 1250895 (CVE-2023-53484) - VUL-0: CVE-2023-53484: kernel: lib: cpu_rmap: Avoid use after free on rmap->obj array entries
Summary: VUL-0: CVE-2023-53484: kernel: lib: cpu_rmap: Avoid use after free on rmap->o...
Status: NEW
Alias: CVE-2023-53484
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents (show other bugs)
Version: unspecified
Hardware: Other Other
: P3 - Medium : Normal
Target Milestone: ---
Deadline: 2025-11-24
Assignee: Security Team bot
QA Contact: Security Team bot
URL: https://smash.suse.de/issue/475207/
Whiteboard: CVSSv3.1:SUSE:CVE-2023-53484:6.2:(AV:...
Keywords:
Depends on:
Blocks:
 
Reported: 2025-10-02 11:53 UTC by SMASH SMASH
Modified: 2025-11-28 15:09 UTC (History)
2 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description SMASH SMASH 2025-10-02 11:53:11 UTC
In the Linux kernel, the following vulnerability has been resolved:

lib: cpu_rmap: Avoid use after free on rmap->obj array entries

When calling irq_set_affinity_notifier() with NULL at the notify
argument, it will cause freeing of the glue pointer in the
corresponding array entry but will leave the pointer in the array. A
subsequent call to free_irq_cpu_rmap() will try to free this entry again
leading to possible use after free.

Fix that by setting NULL to the array entry and checking that we have
non-zero at the array entry when iterating over the array in
free_irq_cpu_rmap().

The current code does not suffer from this since there are no cases
where irq_set_affinity_notifier(irq, NULL) (note the NULL passed for the
notify arg) is called, followed by a call to free_irq_cpu_rmap() so we
don't hit and issue. Subsequent patches in this series excersize this
flow, hence the required fix.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-53484
https://www.cve.org/CVERecord?id=CVE-2023-53484
https://git.kernel.org/stable/c/4e0473f1060aa49621d40a113afde24818101d37
https://git.kernel.org/stable/c/67bca5f1d644f4e79b694abd8052a177de81c37f
https://git.kernel.org/stable/c/981f339d2905b6a92ef59358158b326493aecac5
https://git.kernel.org/stable/c/c6ed54dd90698dc0744d669524cc1c122ded8a16
https://git.kernel.org/stable/c/c9115f49cf260d24d8b5f2d9a4b63cb31a627bb4
https://git.kernel.org/stable/c/cc2d2b3dbfb0ba57bc027fb7e1121250c50e4000
https://git.kernel.org/stable/c/d1308bd0b24cb1d78fa2747d5fa3e055cc628a48
https://git.kernel.org/stable/c/f748e15253833b771acbede14ea98f50831ac289
https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2023/CVE-2023-53484.mbox
https://bugzilla.redhat.com/show_bug.cgi?id=2400792
Comment 2 Takashi Iwai 2025-10-27 14:38:22 UTC
As the fix seems pretty straightforward and cleanly applicable, I backported it to SLE12-SP5 and SLE12-SP3-TD branches.
It had the follow-up fix commit 7c5d4801ecf0, and this was backported as well.
Comment 7 Maintenance Automation 2025-11-24 12:31:15 UTC
SUSE-SU-2025:4189-1: An update that solves 137 vulnerabilities, contains two features and has 12 security fixes can now be installed.

URL: https://www.suse.com/support/update/announcement/2025/suse-su-20254189-1
Category: security (important)
Bug References: 1065729, 1154048, 1205128, 1210124, 1212175, 1213747, 1215136, 1215152, 1223475, 1235485, 1247518, 1248211, 1249161, 1249169, 1249182, 1249203, 1249215, 1249224, 1249260, 1249265, 1249285, 1249302, 1249317, 1249506, 1249512, 1249682, 1249702, 1249721, 1249747, 1249752, 1249806, 1249820, 1249854, 1249859, 1249863, 1249916, 1249941, 1250032, 1250040, 1250074, 1250107, 1250137, 1250163, 1250164, 1250202, 1250211, 1250261, 1250274, 1250277, 1250311, 1250329, 1250400, 1250455, 1250704, 1250741, 1250742, 1250764, 1250768, 1250784, 1250839, 1250840, 1250850, 1250895, 1250919, 1250946, 1250964, 1251035, 1251036, 1251051, 1251052, 1251053, 1251059, 1251061, 1251066, 1251072, 1251080, 1251086, 1251088, 1251091, 1251099, 1251100, 1251113, 1251123, 1251128, 1251129, 1251132, 1251161, 1251166, 1251177, 1251180, 1251182, 1251197, 1251202, 1251208, 1251210, 1251230, 1251283, 1251286, 1251292, 1251293, 1251294, 1251300, 1251325, 1251329, 1251330, 1251333, 1251522, 1251524, 1251550, 1251725, 1251732, 1251736, 1251741, 1251743, 1251750, 1251761, 1251769, 1251772, 1251777, 1251780, 1251804, 1251930, 1252035, 1252039, 1252047, 1252051, 1252052, 1252056, 1252265, 1252480, 1252487, 1252499, 1252513, 1252538, 1252539, 1252545, 1252549, 1252554, 1252560, 1252632, 1252685, 1252688, 1252775, 1252785, 1252789, 1252822, 1252893, 1252904, 1252909
CVE References: CVE-2021-4460, CVE-2022-43945, CVE-2022-48631, CVE-2022-50236, CVE-2022-50249, CVE-2022-50280, CVE-2022-50293, CVE-2022-50327, CVE-2022-50350, CVE-2022-50356, CVE-2022-50367, CVE-2022-50394, CVE-2022-50395, CVE-2022-50423, CVE-2022-50443, CVE-2022-50459, CVE-2022-50470, CVE-2022-50481, CVE-2022-50485, CVE-2022-50487, CVE-2022-50493, CVE-2022-50496, CVE-2022-50501, CVE-2022-50504, CVE-2022-50505, CVE-2022-50509, CVE-2022-50516, CVE-2022-50532, CVE-2022-50534, CVE-2022-50536, CVE-2022-50537, CVE-2022-50542, CVE-2022-50544, CVE-2022-50549, CVE-2022-50563, CVE-2022-50564, CVE-2022-50571, CVE-2022-50581, CVE-2023-53183, CVE-2023-53185, CVE-2023-53188, CVE-2023-53191, CVE-2023-53204, CVE-2023-53271, CVE-2023-53282, CVE-2023-53289, CVE-2023-53292, CVE-2023-53338, CVE-2023-53339, CVE-2023-53373, CVE-2023-53433, CVE-2023-53476, CVE-2023-53477, CVE-2023-53484, CVE-2023-53517, CVE-2023-53519, CVE-2023-53533, CVE-2023-53540, CVE-2023-53548, CVE-2023-53556, CVE-2023-53559, CVE-2023-53564, CVE-2023-53568, CVE-2023-53582, CVE-2023-53587, CVE-2023-53589, CVE-2023-53593, CVE-2023-53594, CVE-2023-53596, CVE-2023-53603, CVE-2023-53604, CVE-2023-53611, CVE-2023-53615, CVE-2023-53619, CVE-2023-53620, CVE-2023-53622, CVE-2023-53624, CVE-2023-53635, CVE-2023-53644, CVE-2023-53647, CVE-2023-53648, CVE-2023-53650, CVE-2023-53667, CVE-2023-53668, CVE-2023-53672, CVE-2023-53675, CVE-2023-53681, CVE-2023-53683, CVE-2023-53687, CVE-2023-53695, CVE-2023-53696, CVE-2023-53705, CVE-2023-53707, CVE-2023-53715, CVE-2023-53717, CVE-2023-53722, CVE-2023-53733, CVE-2023-7324, CVE-2024-56633, CVE-2025-38539, CVE-2025-38680, CVE-2025-38691, CVE-2025-38695, CVE-2025-38699, CVE-2025-38700, CVE-2025-38714, CVE-2025-38718, CVE-2025-38724, CVE-2025-39676, CVE-2025-39702, CVE-2025-39724, CVE-2025-39756, CVE-2025-39772, CVE-2025-39812, CVE-2025-39813, CVE-2025-39841, CVE-2025-39866, CVE-2025-39876, CVE-2025-39911, CVE-2025-39923, CVE-2025-39929, CVE-2025-39931, CVE-2025-39945, CVE-2025-39949, CVE-2025-39955, CVE-2025-39968, CVE-2025-39970, CVE-2025-39971, CVE-2025-39972, CVE-2025-39973, CVE-2025-39997, CVE-2025-40018, CVE-2025-40044, CVE-2025-40049, CVE-2025-40078, CVE-2025-40082, CVE-2025-40088
Jira References: PED-4593, PED-568
Maintenance Incident: [SUSE:Maintenance:41494](https://smelt.suse.de/incident/41494/)
Sources used:
SUSE Linux Enterprise Server 12 SP5 LTSS (src):
 kernel-syms-4.12.14-122.280.1, kernel-source-4.12.14-122.280.1
SUSE Linux Enterprise Server 12 SP5 LTSS Extended Security (src):
 kernel-syms-4.12.14-122.280.1, kernel-source-4.12.14-122.280.1
SUSE Linux Enterprise Live Patching 12-SP5 (src):
 kgraft-patch-SLE12-SP5_Update_74-1-8.5.1

NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.