Bug 2324583 (CVE-2024-50210) - CVE-2024-50210 kernel: posix-clock: posix-clock: Fix unbalanced locking in pc_clock_settime()
Summary: CVE-2024-50210 kernel: posix-clock: posix-clock: Fix unbalanced locking in pc...
Keywords:
Status: NEW
Alias: CVE-2024-50210
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2324691
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-11-08 13:46 UTC by OSIDB Bzimport
Modified: 2024-11-21 15:33 UTC (History)
4 users (show)

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


Attachments (Terms of Use)

Description OSIDB Bzimport 2024-11-08 13:46:48 UTC
In the Linux kernel, the following vulnerability has been resolved:

posix-clock: posix-clock: Fix unbalanced locking in pc_clock_settime()

If get_clock_desc() succeeds, it calls fget() for the clockid's fd,
and get the clk->rwsem read lock, so the error path should release
the lock to make the lock balance and fput the clockid's fd to make
the refcount balance and release the fd related resource.

However the below commit left the error path locked behind resulting in
unbalanced locking. Check timespec64_valid_strict() before
get_clock_desc() to fix it, because the "ts" is not changed
after that.

[pabeni: fixed commit message typo]


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