posix-clock: posix-clock: Fix unbalanced locking in pc_clock_settime()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ a3f169e398215e71361774d13bf91a0101283ac2 · < 1ba33b327c3f88a7baee598979d73ab5b44d41cc| No fix yet |
| Linux Linux |
| No fix yet |
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@redhat.com: fixed commit message typo]
From the CVE record · Linux
The Linux kernel’s posix-clock code can leave a lock held and a file descriptor reference unreleased when pc_clock_settime() receives an invalid timespec after obtaining a clock descriptor. A caller that reaches this error path can trigger unbalanced locking; the input does not specify further impact or authentication requirements.
Engineers running the Linux kernel should check their versions against the vendor advisory; affected versions are not specified in the input.