CVE-2021-47583

Source
https://cve.org/CVERecord?id=CVE-2021-47583
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2021-47583.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2021-47583
Downstream
Related
Published
2024-06-19T15:15:52.843Z
Modified
2026-03-14T14:51:57.206060Z
Severity
  • 5.5 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
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

Git /

Affected ranges

Database specific

unresolved_ranges
[
    {
        "events": [
            {
                "introduced": "3.7"
            },
            {
                "fixed": "4.19.222"
            }
        ]
    },
    {
        "events": [
            {
                "introduced": "4.20"
            },
            {
                "fixed": "5.4.168"
            }
        ]
    },
    {
        "events": [
            {
                "introduced": "5.5"
            },
            {
                "fixed": "5.10.88"
            }
        ]
    },
    {
        "events": [
            {
                "introduced": "5.11"
            },
            {
                "fixed": "5.15.11"
            }
        ]
    }
]
source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2021-47583.json"