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

exploitDog

github логотип

GHSA-mhrv-mcvx-mvx7

Опубликовано: 27 сент. 2024
Источник: github
Github: Не прошло ревью
CVSS3: 5.5

Описание

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

usbnet: ipheth: do not stop RX on failing RX callback

RX callbacks can fail for multiple reasons:

  • Payload too short
  • Payload formatted incorrecly (e.g. bad NCM framing)
  • Lack of memory

None of these should cause the driver to seize up.

Make such failures non-critical and continue processing further incoming URBs.

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

usbnet: ipheth: do not stop RX on failing RX callback

RX callbacks can fail for multiple reasons:

  • Payload too short
  • Payload formatted incorrecly (e.g. bad NCM framing)
  • Lack of memory

None of these should cause the driver to seize up.

Make such failures non-critical and continue processing further incoming URBs.

EPSS

Процентиль: 4%
0.00019
Низкий

5.5 Medium

CVSS3

Связанные уязвимости

CVSS3: 5.5
ubuntu
больше 1 года назад

In the Linux kernel, the following vulnerability has been resolved: usbnet: ipheth: do not stop RX on failing RX callback RX callbacks can fail for multiple reasons: * Payload too short * Payload formatted incorrecly (e.g. bad NCM framing) * Lack of memory None of these should cause the driver to seize up. Make such failures non-critical and continue processing further incoming URBs.

CVSS3: 5.5
redhat
больше 1 года назад

In the Linux kernel, the following vulnerability has been resolved: usbnet: ipheth: do not stop RX on failing RX callback RX callbacks can fail for multiple reasons: * Payload too short * Payload formatted incorrecly (e.g. bad NCM framing) * Lack of memory None of these should cause the driver to seize up. Make such failures non-critical and continue processing further incoming URBs.

CVSS3: 5.5
nvd
больше 1 года назад

In the Linux kernel, the following vulnerability has been resolved: usbnet: ipheth: do not stop RX on failing RX callback RX callbacks can fail for multiple reasons: * Payload too short * Payload formatted incorrecly (e.g. bad NCM framing) * Lack of memory None of these should cause the driver to seize up. Make such failures non-critical and continue processing further incoming URBs.

CVSS3: 5.5
msrc
около 1 года назад

usbnet: ipheth: do not stop RX on failing RX callback

CVSS3: 5.5
debian
больше 1 года назад

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

EPSS

Процентиль: 4%
0.00019
Низкий

5.5 Medium

CVSS3