CVE-2022-49304

See a problem?
Please try reporting it to the source first.
Source
https://nvd.nist.gov/vuln/detail/CVE-2022-49304
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49304.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2022-49304
Related
Published
2025-02-26T07:01:07Z
Modified
2025-02-26T19:01:09.955670Z
Summary
[none]
Details

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

drivers: tty: serial: Fix deadlock in sa1100settermios()

There is a deadlock in sa1100settermios(), which is shown below:

(Thread 1) | (Thread 2) | sa1100enablems() sa1100settermios() | modtimer() spinlockirqsave() //(1) | (wait a time) ... | sa1100timeout() deltimersync() | spinlockirqsave() //(2) (wait timer to stop) | ...

We hold sport->port.lock in position (1) of thread 1 and use deltimersync() to wait timer to stop, but timer handler also need sport->port.lock in position (2) of thread 2. As a result, sa1100settermios() will block forever.

This patch moves deltimersync() before spinlockirqsave() in order to prevent the deadlock.

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.127-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
5.10.92-1
5.10.92-2
5.10.103-1~bpo10+1
5.10.103-1
5.10.106-1
5.10.113-1
5.10.120-1~bpo10+1
5.10.120-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.18.5-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.18.5-1

Ecosystem specific 

{
    "urgency": "not yet assigned"
}