Bug 2189388 (CVE-2023-2269) - CVE-2023-2269 kernel: A possible deadlock in dm_get_inactive_table in dm- ioctl.c leads to dos
Summary: CVE-2023-2269 kernel: A possible deadlock in dm_get_inactive_table in dm- io...
Keywords:
Status: NEW
Alias: CVE-2023-2269
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On: 2189389 2189390 2189391 2189392 2189394
Blocks: 2189387
TreeView+ depends on / blocked
 
Reported: 2023-04-25 05:07 UTC by Rohit Keshri
Modified: 2024-01-04 13:52 UTC (History)
50 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in the Linux Kernel, leading to a denial of service. This issue occurs due to a possible recursive locking scenario, resulting in a deadlock in table_clear in drivers/md/dm-ioctl.c in the Linux Kernel Device Mapper-Multipathing sub-component.
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)

Description Rohit Keshri 2023-04-25 05:07:40 UTC 
A bug in the Linux kernel version 6.2.0 by syzkaller with our own templates. The bug causes a
possible recursive locking scenario, resulting in a deadlock.

The key trace is as follows:

down_read+0x9d/0x450 kernel/locking/rwsem.c:1509
dm_get_inactive_table+0x2b/0xc0 drivers/md/dm-ioctl.c:773
__dev_status+0x4fd/0x7c0 drivers/md/dm-ioctl.c:844
table_clear+0x197/0x280 drivers/md/dm-ioctl.c:1537

In table_clear, it acquires a write lock
https://elixir.bootlin.com/linux/v6.2/source/drivers/md/dm-ioctl.c#L1520
down_write(&_hash_lock);

Then before the lock is released at L1539, there is a path shown above:
table_clear -> __dev_status -> dm_get_inactive_table -> down_read

https://elixir.bootlin.com/linux/v6.2/source/drivers/md/dm-ioctl.c#L773
down_read(&_hash_lock);

It tries to acquire the same read lock again, resulting in the deadlock problem
Comment 3 Rohit Keshri 2023-04-25 05:33:21 UTC 
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 2189394]
Note You need to log in before you can comment on or make changes to this bug.