CVE-2021-47583

See a problem?

Source

https://nvd.nist.gov/vuln/detail/CVE-2021-47583

Import Source

https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2021-47583.json

JSON Data

https://api.osv.dev/v1/vulns/CVE-2021-47583

Related

Published

2024-06-19T15:15:52Z

Modified

2024-09-11T04:41:14.644199Z

Summary

[none]

Details

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

media: mxl111sf: change mutex_init() location

Syzbot reported, that mxl111sfctrlmsg() uses uninitialized mutex. The problem was in wrong mutex_init() location.

Previous mutexinit(&state->msglock) call was in ->init() function, but dvbusbv2init() has this order of calls:

dvb_usbv2_init()
  dvb_usbv2_adapter_init()
    dvb_usbv2_adapter_frontend_init()
      props->frontend_attach()

  props->init()

Since mxl111sf* devices call mxl111sfctrlmsg() in ->frontendattach() internally we need to initialize state->msglock before frontendattach(). To achieve it, ->probe() call added to all mxl111sf_* devices, which will simply initiaize mutex.

References

Affected packages

Debian:11 / linux

Package

Name: linux
Purl: pkg:deb/debian/linux?arch=source

Affected ranges

Type: ECOSYSTEM
Events: Introduced

0Unknown introduced version / All previous versions are affected

Fixed

5.10.92-1

Affected versions

5.*

5.10.46-4

5.10.46-5

5.10.70-1~bpo10+1

5.10.70-1

5.10.84-1

5.10.92-1~bpo10+1

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:12 / linux

Package

Name: linux
Purl: pkg:deb/debian/linux?arch=source

Affected ranges

Type: ECOSYSTEM
Events: Introduced

0Unknown introduced version / All previous versions are affected

Fixed

5.15.15-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:13 / linux

Package

Name: linux
Purl: pkg:deb/debian/linux?arch=source

Affected ranges

Type: ECOSYSTEM
Events: Introduced

0Unknown introduced version / All previous versions are affected

Fixed

5.15.15-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}