Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

Поиск уязвимостей

Количество 15

Количество 15

fstec логотип

BDU:2026-13736

10 месяцев назад

Уязвимость функции regulator_resolve_supply() модуля drivers/regulator/core.c драйвера регуляторов напряжения и тока ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании

CVSS3: 5.5
EPSS: Низкий
redos логотип

ROS-20261014-80-0101

около 1 месяца назад

Уязвимость kernel-lt

CVSS3: 5.5
EPSS: Низкий
redos логотип

ROS-20261014-73-0100

около 1 месяца назад

Уязвимость kernel-lt

CVSS3: 5.5
EPSS: Низкий
ubuntu логотип

CVE-2026-46252

6 месяцев назад

In the Linux kernel, the following vulnerability has been resolved: regulator: core: fix locking in regulator_resolve_supply() error path If late enabling of a supply regulator fails in regulator_resolve_supply(), the code currently triggers a lockdep warning: WARNING: drivers/regulator/core.c:2649 at _regulator_put+0x80/0xa0, CPU#6: kworker/u32:4/596 ... Call trace: _regulator_put+0x80/0xa0 (P) regulator_resolve_supply+0x7cc/0xbe0 regulator_register_resolve_supply+0x28/0xb8 as the regulator_list_mutex must be held when calling _regulator_put(). To solve this, simply switch to using regulator_put(). While at it, we should also make sure that no concurrent access happens to our rdev while we clear out the supply pointer. Add appropriate locking to ensure that. While the code in question will be removed altogether in a follow-up commit, I believe it is still beneficial to have this corrected before removal for future reference.

CVSS3: 5.5
EPSS: Низкий
redhat логотип

CVE-2026-46252

6 месяцев назад

In the Linux kernel, the following vulnerability has been resolved: regulator: core: fix locking in regulator_resolve_supply() error path If late enabling of a supply regulator fails in regulator_resolve_supply(), the code currently triggers a lockdep warning: WARNING: drivers/regulator/core.c:2649 at _regulator_put+0x80/0xa0, CPU#6: kworker/u32:4/596 ... Call trace: _regulator_put+0x80/0xa0 (P) regulator_resolve_supply+0x7cc/0xbe0 regulator_register_resolve_supply+0x28/0xb8 as the regulator_list_mutex must be held when calling _regulator_put(). To solve this, simply switch to using regulator_put(). While at it, we should also make sure that no concurrent access happens to our rdev while we clear out the supply pointer. Add appropriate locking to ensure that. While the code in question will be removed altogether in a follow-up commit, I believe it is still beneficial to have this corrected before removal for future reference.

CVSS3: 5.5
EPSS: Низкий
nvd логотип

CVE-2026-46252

6 месяцев назад

In the Linux kernel, the following vulnerability has been resolved: regulator: core: fix locking in regulator_resolve_supply() error path If late enabling of a supply regulator fails in regulator_resolve_supply(), the code currently triggers a lockdep warning: WARNING: drivers/regulator/core.c:2649 at _regulator_put+0x80/0xa0, CPU#6: kworker/u32:4/596 ... Call trace: _regulator_put+0x80/0xa0 (P) regulator_resolve_supply+0x7cc/0xbe0 regulator_register_resolve_supply+0x28/0xb8 as the regulator_list_mutex must be held when calling _regulator_put(). To solve this, simply switch to using regulator_put(). While at it, we should also make sure that no concurrent access happens to our rdev while we clear out the supply pointer. Add appropriate locking to ensure that. While the code in question will be removed altogether in a follow-up commit, I believe it is still beneficial to have this corrected before removal for future reference.

CVSS3: 5.5
EPSS: Низкий
msrc логотип

CVE-2026-46252

5 месяцев назад

regulator: core: fix locking in regulator_resolve_supply() error path

EPSS: Низкий
debian логотип

CVE-2026-46252

6 месяцев назад

In the Linux kernel, the following vulnerability has been resolved: r ...

CVSS3: 5.5
EPSS: Низкий
github логотип

GHSA-w447-hxj8-xq6p

6 месяцев назад

In the Linux kernel, the following vulnerability has been resolved: regulator: core: fix locking in regulator_resolve_supply() error path If late enabling of a supply regulator fails in regulator_resolve_supply(), the code currently triggers a lockdep warning: WARNING: drivers/regulator/core.c:2649 at _regulator_put+0x80/0xa0, CPU#6: kworker/u32:4/596 ... Call trace: _regulator_put+0x80/0xa0 (P) regulator_resolve_supply+0x7cc/0xbe0 regulator_register_resolve_supply+0x28/0xb8 as the regulator_list_mutex must be held when calling _regulator_put(). To solve this, simply switch to using regulator_put(). While at it, we should also make sure that no concurrent access happens to our rdev while we clear out the supply pointer. Add appropriate locking to ensure that. While the code in question will be removed altogether in a follow-up commit, I believe it is still beneficial to have this corrected before removal for future reference.

CVSS3: 5.5
EPSS: Низкий
suse-cvrf логотип

SUSE-SU-2026:3594-1

3 месяца назад

Security update for the Linux Kernel

EPSS: Низкий
oracle-oval логотип

ELBA-2026-500163

3 месяца назад

ELBA-2026-500163: Unbreakable Enterprise kernel bug fix update (NA)

EPSS: Низкий
suse-cvrf логотип

SUSE-SU-2026:3166-1

4 месяца назад

Security update for the Linux Kernel

EPSS: Низкий
suse-cvrf логотип

SUSE-SU-2026:3130-1

4 месяца назад

Security update for the Linux Kernel

EPSS: Низкий
suse-cvrf логотип

openSUSE-SU-2026:21555-1

3 месяца назад

Security update for the Linux Kernel

EPSS: Низкий
oracle-oval логотип

ELSA-2026-500248

3 месяца назад

ELSA-2026-500248: Unbreakable Enterprise kernel security update (IMPORTANT)

EPSS: Низкий

Уязвимостей на страницу

Уязвимость
CVSS
EPSS
Опубликовано
fstec логотип
BDU:2026-13736

Уязвимость функции regulator_resolve_supply() модуля drivers/regulator/core.c драйвера регуляторов напряжения и тока ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании

CVSS3: 5.5
0%
Низкий
10 месяцев назад
redos логотип
ROS-20261014-80-0101

Уязвимость kernel-lt

CVSS3: 5.5
0%
Низкий
около 1 месяца назад
redos логотип
ROS-20261014-73-0100

Уязвимость kernel-lt

CVSS3: 5.5
0%
Низкий
около 1 месяца назад
ubuntu логотип
CVE-2026-46252

In the Linux kernel, the following vulnerability has been resolved: regulator: core: fix locking in regulator_resolve_supply() error path If late enabling of a supply regulator fails in regulator_resolve_supply(), the code currently triggers a lockdep warning: WARNING: drivers/regulator/core.c:2649 at _regulator_put+0x80/0xa0, CPU#6: kworker/u32:4/596 ... Call trace: _regulator_put+0x80/0xa0 (P) regulator_resolve_supply+0x7cc/0xbe0 regulator_register_resolve_supply+0x28/0xb8 as the regulator_list_mutex must be held when calling _regulator_put(). To solve this, simply switch to using regulator_put(). While at it, we should also make sure that no concurrent access happens to our rdev while we clear out the supply pointer. Add appropriate locking to ensure that. While the code in question will be removed altogether in a follow-up commit, I believe it is still beneficial to have this corrected before removal for future reference.

CVSS3: 5.5
0%
Низкий
6 месяцев назад
redhat логотип
CVE-2026-46252

In the Linux kernel, the following vulnerability has been resolved: regulator: core: fix locking in regulator_resolve_supply() error path If late enabling of a supply regulator fails in regulator_resolve_supply(), the code currently triggers a lockdep warning: WARNING: drivers/regulator/core.c:2649 at _regulator_put+0x80/0xa0, CPU#6: kworker/u32:4/596 ... Call trace: _regulator_put+0x80/0xa0 (P) regulator_resolve_supply+0x7cc/0xbe0 regulator_register_resolve_supply+0x28/0xb8 as the regulator_list_mutex must be held when calling _regulator_put(). To solve this, simply switch to using regulator_put(). While at it, we should also make sure that no concurrent access happens to our rdev while we clear out the supply pointer. Add appropriate locking to ensure that. While the code in question will be removed altogether in a follow-up commit, I believe it is still beneficial to have this corrected before removal for future reference.

CVSS3: 5.5
0%
Низкий
6 месяцев назад
nvd логотип
CVE-2026-46252

In the Linux kernel, the following vulnerability has been resolved: regulator: core: fix locking in regulator_resolve_supply() error path If late enabling of a supply regulator fails in regulator_resolve_supply(), the code currently triggers a lockdep warning: WARNING: drivers/regulator/core.c:2649 at _regulator_put+0x80/0xa0, CPU#6: kworker/u32:4/596 ... Call trace: _regulator_put+0x80/0xa0 (P) regulator_resolve_supply+0x7cc/0xbe0 regulator_register_resolve_supply+0x28/0xb8 as the regulator_list_mutex must be held when calling _regulator_put(). To solve this, simply switch to using regulator_put(). While at it, we should also make sure that no concurrent access happens to our rdev while we clear out the supply pointer. Add appropriate locking to ensure that. While the code in question will be removed altogether in a follow-up commit, I believe it is still beneficial to have this corrected before removal for future reference.

CVSS3: 5.5
0%
Низкий
6 месяцев назад
msrc логотип
CVE-2026-46252

regulator: core: fix locking in regulator_resolve_supply() error path

0%
Низкий
5 месяцев назад
debian логотип
CVE-2026-46252

In the Linux kernel, the following vulnerability has been resolved: r ...

CVSS3: 5.5
0%
Низкий
6 месяцев назад
github логотип
GHSA-w447-hxj8-xq6p

In the Linux kernel, the following vulnerability has been resolved: regulator: core: fix locking in regulator_resolve_supply() error path If late enabling of a supply regulator fails in regulator_resolve_supply(), the code currently triggers a lockdep warning: WARNING: drivers/regulator/core.c:2649 at _regulator_put+0x80/0xa0, CPU#6: kworker/u32:4/596 ... Call trace: _regulator_put+0x80/0xa0 (P) regulator_resolve_supply+0x7cc/0xbe0 regulator_register_resolve_supply+0x28/0xb8 as the regulator_list_mutex must be held when calling _regulator_put(). To solve this, simply switch to using regulator_put(). While at it, we should also make sure that no concurrent access happens to our rdev while we clear out the supply pointer. Add appropriate locking to ensure that. While the code in question will be removed altogether in a follow-up commit, I believe it is still beneficial to have this corrected before removal for future reference.

CVSS3: 5.5
0%
Низкий
6 месяцев назад
suse-cvrf логотип
SUSE-SU-2026:3594-1

Security update for the Linux Kernel

3 месяца назад
oracle-oval логотип
ELBA-2026-500163

ELBA-2026-500163: Unbreakable Enterprise kernel bug fix update (NA)

3 месяца назад
suse-cvrf логотип
SUSE-SU-2026:3166-1

Security update for the Linux Kernel

4 месяца назад
suse-cvrf логотип
SUSE-SU-2026:3130-1

Security update for the Linux Kernel

4 месяца назад
suse-cvrf логотип
openSUSE-SU-2026:21555-1

Security update for the Linux Kernel

3 месяца назад
oracle-oval логотип
ELSA-2026-500248

ELSA-2026-500248: Unbreakable Enterprise kernel security update (IMPORTANT)

3 месяца назад

Уязвимостей на страницу