Bug 2348344 (CVE-2022-49085) - CVE-2022-49085 kernel: drbd: Fix five use after free bugs in get_initial_state
Summary: CVE-2022-49085 kernel: drbd: Fix five use after free bugs in get_initial_state
Keywords:
Status: NEW
Alias: CVE-2022-49085
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-02-26 03:26 UTC by OSIDB Bzimport
Modified: 2025-02-26 09:15 UTC (History)
4 users (show)

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


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-02-26 03:26:10 UTC
In the Linux kernel, the following vulnerability has been resolved:

drbd: Fix five use after free bugs in get_initial_state

In get_initial_state, it calls notify_initial_state_done(skb,..) if
cb->args[5]==1. If genlmsg_put() failed in notify_initial_state_done(),
the skb will be freed by nlmsg_free(skb).
Then get_initial_state will goto out and the freed skb will be used by
return value skb->len, which is a uaf bug.

What's worse, the same problem goes even further: skb can also be
freed in the notify_*_state_change -> notify_*_state calls below.
Thus 4 additional uaf bugs happened.

My patch lets the problem callee functions: notify_initial_state_done
and notify_*_state_change return an error code if errors happen.
So that the error codes could be propagated and the uaf bugs can be avoid.

v2 reports a compilation warning. This v3 fixed this warning and built
successfully in my local environment with no additional warnings.
v2: https://lore.kernel.org/patchwork/patch/1435218/

Comment 1 Avinash Hanwate 2025-02-26 07:38:51 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025022657-CVE-2022-49085-a9d4@gregkh/T

Comment 5 Avinash Hanwate 2025-02-26 09:11:02 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025022657-CVE-2022-49085-a9d4@gregkh/T


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