LiveActive security incident?Get immediate response
CVE Record

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

In the Linux kernel, the following vulnerability has been resolved: net: lapbether: fix issue of invalid opcode in lapbeth_open() If lapb_register() 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:napi_enable+0x16a/0x1f0 [ 1958.332310][T11356] Call Trace: [ 1958.332817][T11356] <TASK> [ 1958.336135][T11356] lapbeth_open+0x18/0x90 [ 1958.337446][T11356] __dev_open+0x258/0x490 [ 1958.341672][T11356] __dev_change_flags+0x4d4/0x6a0 [ 1958.345325][T11356] dev_change_flags+0x93/0x160 [ 1958.346027][T11356] devinet_ioctl+0x1276/0x1bf0 [ 1958.346738][T11356] inet_ioctl+0x1c8/0x2d0 [ 1958.349638][T11356] sock_ioctl+0x5d1/0x750 [ 1958.356059][T11356] __x64_sys_ioctl+0x3ec/0x1790 [ 1958.365594][T11356] do_syscall_64+0x35/0x80 [ 1958.366239][T11356] entry_SYSCALL_64_after_hwframe+0x46/0xb0 [ 1958.377381][T11356] </TASK>

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash a system path when a LAPB-over-Ethernet device is brought up after an earlier registration failure. The public record describes a kernel BUG and invalid opcode, which points primarily to availability risk. Exposure appears limited to systems using or enabling the lapbether driver.

Executive priority

Treat as a targeted availability issue, not a broad internet-facing emergency based on current evidence. Patch through normal kernel maintenance, with faster handling for environments using LAPB-over-Ethernet or specialized networking stacks.

Technical view

In lapbeth_open(), a failed lapb_register() path left NAPI enabled state inconsistent. On a later device-up attempt, napi_enable() hit a kernel BUG in net/core/dev.c. The fix is in upstream stable kernel commits referenced by the CVE record. Public sources do not provide CVSS, CWE, or distro-specific package status.

Likely exposure

Likely exposed systems are Linux hosts running affected kernel versions where the lapbether driver is present and LAPB-over-Ethernet interfaces are configured or can be enabled. General Linux servers that do not use this niche networking driver appear less likely to be affected, based on the provided record.

Exploitation context

No active exploitation is cited, and the CVE is not marked KEV. The source bundle shows a crash triggered during device state changes after a prior failure, but does not establish remote exploitability, privilege requirements, or real-world exploitation.

Researcher notes

The record lacks CVSS, CWE, distro matrices, and exploitability details. Analysis should focus on the lapb_register() failure path, NAPI state cleanup, and whether local administrative control is required to exercise the device-up sequence.

Mitigation direction

  • Apply a vendor kernel update containing the referenced stable lapbether fixes.
  • Check distribution advisories for the exact fixed package version.
  • Prioritize systems using LAPB-over-Ethernet or custom kernel networking configurations.
  • If patching is delayed, follow vendor guidance; no source-provided workaround is named.

Validation and detection

  • Inventory Linux kernel versions against vendor fixed versions and upstream stable references.
  • Confirm whether lapbether support is built, loaded, or operationally required.
  • Review kernel package changelogs for the referenced stable commit backports.
  • Test affected workflows in staging after updating the kernel.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-49859 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux514e1150da9cd8d7978d990a353636cf1a7a87c2, 514e1150da9cd8d7978d990a353636cf1a7a87c2, 514e1150da9cd8d7978d990a353636cf1a7a87c2unaffected
LinuxLinux5.13, 0, 5.15.79, 6.0.9, 6.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.