CVE-2022-49859: net: lapbether: fix issue of invalid opcode in lapbeth_open()

Q: What is the severity of CVE-2022-49859?

CVE-2022-49859 is considered to have a moderate severity due to the potential for an invalid opcode issue in the Linux kernel.

Q: How do I fix CVE-2022-49859?

To fix CVE-2022-49859, update to the latest version of the Linux kernel that has patched this vulnerability.

Q: What components are affected by CVE-2022-49859?

CVE-2022-49859 affects the net subsystem specifically related to the lapb device management in the Linux kernel.

Q: Is CVE-2022-49859 a remote exploit?

CVE-2022-49859 is not categorized as a remote exploit; it pertains to local device management in the kernel.

Q: What impact does CVE-2022-49859 have on system stability?

CVE-2022-49859 can lead to system instability due to the occurrence of an invalid opcode in the lapb protocol handling.

Published May 1, 2025

Updated

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

net: lapbether: fix issue of invalid opcode in lapbethopen()

If lapbregister() failed when lapb device goes to up for the first time, the NAPI is not disabled. As a result, the invalid opcode issue is reported when the lapb device goes to up for the second time.

The stack info is as follows: [ 1958.311422][T11356] kernel BUG at net/core/dev.c:6442! [ 1958.312206][T11356] invalid opcode: 0000 [#1] PREEMPT SMP KASAN [ 1958.315979][T11356] RIP: 0010:napienable+0x16a/0x1f0 [ 1958.332310][T11356] Call Trace: [ 1958.332817][T11356] <TASK> [ 1958.336135][T11356] lapbethopen+0x18/0x90 [ 1958.337446][T11356] devopen+0x258/0x490 [ 1958.341672][T11356] devchangeflags+0x4d4/0x6a0 [ 1958.345325][T11356] devchangeflags+0x93/0x160 [ 1958.346027][T11356] devinetioctl+0x1276/0x1bf0 [ 1958.346738][T11356] inetioctl+0x1c8/0x2d0 [ 1958.349638][T11356] sockioctl+0x5d1/0x750 [ 1958.356059][T11356] x64sysioctl+0x3ec/0x1790 [ 1958.365594][T11356] dosyscall64+0x35/0x80 [ 1958.366239][T11356] entrySYSCALL64afterhwframe+0x46/0xb0 [ 1958.377381][T11356] </TASK>

Affected Software

116 affected componentsFixes available

Linux Linux kernel

Linux Linux kernel>=5.13<5.15.79

Linux Linux kernel>=5.16<6.0.9

Linux Linux kernel=6.1-rc1

Linux Linux kernel=6.1-rc2

Linux Linux kernel=6.1-rc3

Linux Linux kernel=6.1-rc4

debian/linux<6.0.10-1

6.0.10-1

debian/linux<6.0.10-1

6.0.10-1

debian/linux<6.0.10-1

6.0.10-1

debian/linux

6.1.176-16.1.190-16.12.107-16.12.115-27.2.12-17.2.15-1

ubuntu/linux-hwe-edge*

ubuntu/linux-aws-5.0*

ubuntu/linux-aws-5.3*

ubuntu/linux-azure*

ubuntu/linux-azure-5.3*

ubuntu/linux-azure-edge*

ubuntu/linux-gcp*

ubuntu/linux-gcp-5.3*

ubuntu/linux-gke-4.15*

ubuntu/linux-gke-5.4*

ubuntu/linux-gkeop-5.4*

ubuntu/linux-hwe*

ubuntu/linux-hwe-edge*

ubuntu/linux-oem*

ubuntu/linux-oracle-5.0*

ubuntu/linux-oracle-5.3*

ubuntu/linux-aws-5.15<5.15.0-1031.35~20.04.1

5.15.0-1031.35~20.04.1

ubuntu/linux-azure-5.15<5.15.0-1034.41~20.04.1

5.15.0-1034.41~20.04.1

ubuntu/linux-gcp-5.15<5.15.0-1030.37~20.04.1

5.15.0-1030.37~20.04.1

ubuntu/linux-hwe-5.15<5.15.0-67.74~20.04.1

5.15.0-67.74~20.04.1

ubuntu/linux-intel-iotg-5.15<5.15.0-1026.31~20.04.1

5.15.0-1026.31~20.04.1

ubuntu/linux-lowlatency-hwe-5.15<5.15.0-67.74~20.04.1

5.15.0-67.74~20.04.1

ubuntu/linux-nvidia-tegra-5.15<5.15.0-1014.14~20.04.1

5.15.0-1014.14~20.04.1

ubuntu/linux-oracle-5.15<5.15.0-1030.36~20.04.1

5.15.0-1030.36~20.04.1

ubuntu/linux-riscv-5.15<5.15.0-1030.34~20.04.1

5.15.0-1030.34~20.04.1

ubuntu/linux-aws-5.11*

ubuntu/linux-aws-5.13*

ubuntu/linux-aws-5.8*

ubuntu/linux-azure-5.11*

ubuntu/linux-azure-5.13*

ubuntu/linux-azure-5.8*

ubuntu/linux-azure-fde*

ubuntu/linux-gcp-5.11*

ubuntu/linux-gcp-5.13*

ubuntu/linux-gcp-5.8*

ubuntu/linux-gke*

ubuntu/linux-gke-5.15*

ubuntu/linux-gkeop*

ubuntu/linux-gkeop-5.15*

ubuntu/linux-hwe-5.11*

ubuntu/linux-hwe-5.13*

ubuntu/linux-hwe-5.8*

ubuntu/linux-intel-5.13*

ubuntu/linux-oem-5.10*

ubuntu/linux-oem-5.13*

ubuntu/linux-oem-5.6*

ubuntu/linux-oracle-5.11*

ubuntu/linux-oracle-5.13*

ubuntu/linux-oracle-5.8*

ubuntu/linux-raspi2*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.11*

ubuntu/linux-riscv-5.8*

ubuntu/linux<5.15.0-67.74

5.15.0-67.74

ubuntu/linux-allwinner-5.19*

ubuntu/linux-aws<5.15.0-1031.35

5.15.0-1031.35

ubuntu/linux-aws-5.19*

ubuntu/linux-aws-6.2*

ubuntu/linux-aws-6.5*

ubuntu/linux-azure<5.15.0-1034.41

5.15.0-1034.41

ubuntu/linux-azure-5.19*

ubuntu/linux-azure-6.2*

ubuntu/linux-azure-6.5*

ubuntu/linux-azure-fde<5.15.0-1034.41.1

5.15.0-1034.41.1

ubuntu/linux-azure-fde-5.19*

ubuntu/linux-azure-fde-6.2*

ubuntu/linux-gcp<5.15.0-1030.37

5.15.0-1030.37

ubuntu/linux-gcp-5.19*

ubuntu/linux-gcp-6.2*

ubuntu/linux-gcp-6.5*

ubuntu/linux-gke<5.15.0-1028.33

5.15.0-1028.33

ubuntu/linux-gkeop<5.15.0-1016.21

5.15.0-1016.21

ubuntu/linux-hwe-5.19*

ubuntu/linux-hwe-6.2*

ubuntu/linux-hwe-6.5*

ubuntu/linux-ibm<5.15.0-1026.29

5.15.0-1026.29

ubuntu/linux-intel-iotg<5.15.0-1026.31

5.15.0-1026.31

ubuntu/linux-kvm<5.15.0-1029.34

5.15.0-1029.34

ubuntu/linux-lowlatency<5.15.0-67.74

5.15.0-67.74

ubuntu/linux-lowlatency-hwe-5.19*

ubuntu/linux-lowlatency-hwe-6.2*

ubuntu/linux-lowlatency-hwe-6.5*

ubuntu/linux-nvidia<5.15.0-1023.23

5.15.0-1023.23

ubuntu/linux-nvidia-6.2*

ubuntu/linux-nvidia-6.5*

ubuntu/linux-oem-5.17*

ubuntu/linux-oem-6.0*

ubuntu/linux-oem-6.1*

ubuntu/linux-oem-6.5*

ubuntu/linux-oracle<5.15.0-1030.36

5.15.0-1030.36

ubuntu/linux-oracle-6.5*

ubuntu/linux-raspi<5.15.0-1025.27

5.15.0-1025.27

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.19*

ubuntu/linux-riscv-6.5*

ubuntu/linux-starfive-5.19*

ubuntu/linux-starfive-6.2*

ubuntu/linux-starfive-6.5*

ubuntu/linux-bluefield<5.15.0-1014.16

5.15.0-1014.16

ubuntu/linux-intel-iot-realtime<5.15.0-1022.27

5.15.0-1022.27

ubuntu/linux-realtime<5.15.0-1033.36

5.15.0-1033.36

ubuntu/linux-raspi-realtime*

ubuntu/linux-realtime*

ubuntu/linux-vmware*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade ubuntu/linux-aws-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1031.35~20.04.1
Upgrade
Upgrade ubuntu/linux-azure-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1034.41~20.04.1
Upgrade
Upgrade ubuntu/linux-gcp-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1030.37~20.04.1
Upgrade
Upgrade ubuntu/linux-hwe-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-67.74~20.04.1
Upgrade
Upgrade ubuntu/linux-intel-iotg-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1026.31~20.04.1
Upgrade
Upgrade ubuntu/linux-lowlatency-hwe-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-67.74~20.04.1
Upgrade
Upgrade ubuntu/linux-nvidia-tegra-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1014.14~20.04.1
Upgrade
Upgrade ubuntu/linux-oracle-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1030.36~20.04.1
Upgrade
Upgrade ubuntu/linux-riscv-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1030.34~20.04.1
Upgrade
Upgrade ubuntu/linux to a version that resolves this vulnerability.
Fixed in 5.15.0-67.74
Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 5.15.0-1031.35
Upgrade
Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.
Fixed in 5.15.0-1034.41
Upgrade
Upgrade ubuntu/linux-azure-fde to a version that resolves this vulnerability.
Fixed in 5.15.0-1034.41.1
Upgrade
Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.
Fixed in 5.15.0-1030.37
Upgrade
Upgrade ubuntu/linux-gke to a version that resolves this vulnerability.
Fixed in 5.15.0-1028.33
Upgrade
Upgrade ubuntu/linux-gkeop to a version that resolves this vulnerability.
Fixed in 5.15.0-1016.21
Upgrade
Upgrade ubuntu/linux-ibm to a version that resolves this vulnerability.
Fixed in 5.15.0-1026.29
Upgrade
Upgrade ubuntu/linux-intel-iotg to a version that resolves this vulnerability.
Fixed in 5.15.0-1026.31
Upgrade
Upgrade ubuntu/linux-kvm to a version that resolves this vulnerability.
Fixed in 5.15.0-1029.34
Upgrade
Upgrade ubuntu/linux-lowlatency to a version that resolves this vulnerability.
Fixed in 5.15.0-67.74
Upgrade
Upgrade ubuntu/linux-nvidia to a version that resolves this vulnerability.
Fixed in 5.15.0-1023.23
Upgrade
Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.
Fixed in 5.15.0-1030.36
Upgrade
Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.
Fixed in 5.15.0-1025.27
Upgrade
Upgrade ubuntu/linux-bluefield to a version that resolves this vulnerability.
Fixed in 5.15.0-1014.16
Upgrade
Upgrade ubuntu/linux-intel-iot-realtime to a version that resolves this vulnerability.
Fixed in 5.15.0-1022.27
Upgrade
Upgrade ubuntu/linux-realtime to a version that resolves this vulnerability.
Fixed in 5.15.0-1033.36
Upgrade
Upgrade debian/linux to a version that resolves this vulnerability.
Fixed in 6.0.10-1
Upgrade
Upgrade debian/linux to a version that resolves this vulnerability.
Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1

Event History

May 1, 2025

CVE Published

via MITRE·02:10 PM

Data Sourced

via MITRE·02:10 PM

Description

Data Sourced

via OSV·03:16 PM

DescriptionSeverityAffected Software

Data Sourced

via NVD·03:16 PM

RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

What is the severity of CVE-2022-49859?

CVE-2022-49859 is considered to have a moderate severity due to the potential for an invalid opcode issue in the Linux kernel.

How do I fix CVE-2022-49859?

To fix CVE-2022-49859, update to the latest version of the Linux kernel that has patched this vulnerability.

What components are affected by CVE-2022-49859?

CVE-2022-49859 affects the net subsystem specifically related to the lapb device management in the Linux kernel.

Is CVE-2022-49859 a remote exploit?

CVE-2022-49859 is not categorized as a remote exploit; it pertains to local device management in the kernel.

What impact does CVE-2022-49859 have on system stability?

CVE-2022-49859 can lead to system instability due to the occurrence of an invalid opcode in the lapb protocol handling.

CVE-2022-49859: net: lapbether: fix issue of invalid opcode in lapbeth_open()

Affected Software

Remediation

Event History

Frequently Asked Questions

What is the severity of CVE-2022-49859?

How do I fix CVE-2022-49859?

What components are affected by CVE-2022-49859?

Is CVE-2022-49859 a remote exploit?

What impact does CVE-2022-49859 have on system stability?

Company

Resources

Contact