LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49727: ipv6: Fix signed integer overflow in l2tp_ip6_sendmsg

In the Linux kernel, the following vulnerability has been resolved: ipv6: Fix signed integer overflow in l2tp_ip6_sendmsg When len >= INT_MAX - transhdrlen, ulen = len + transhdrlen will be overflow. To fix, we can follow what udpv6 does and subtract the transhdrlen from the max.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-49727 is a Linux kernel flaw in IPv6 L2TP message handling. A low-privileged local user may trigger a signed integer overflow that can crash or disrupt the system. It is not described as remote code execution, and the sources do not show active exploitation.

Executive priority

Treat as a routine but real availability risk. Prioritize patching on shared Linux infrastructure and systems where local users are less trusted. It does not warrant emergency response based on the provided evidence alone.

Technical view

The issue is CWE-190 in l2tp_ip6_sendmsg. When len is near INT_MAX, adding transhdrlen can overflow ulen. The kernel fix follows udpv6-style bounds checking by subtracting the transport header length from the maximum allowed length before accepting the message size.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions or downstream builds without the referenced stable fixes. The practical concern is higher on shared systems where low-privileged local users can reach the vulnerable kernel path.

Exploitation context

The CVSS vector is local, low complexity, low privileges, no user interaction, with high availability impact. KEV is false in the provided data. No cited source in the bundle confirms active exploitation or public weaponization.

Researcher notes

The affected component is the IPv6 L2TP sendmsg path. Analysis should focus on kernel builds derived from affected versions and whether the stable commits are present. The source bundle does not provide exploit details, proof of exploitation, or distro-specific fixed package names.

Mitigation direction

  • Update to a vendor-supported kernel containing the referenced stable fixes.
  • Check Linux distribution advisories for fixed package versions.
  • Prioritize shared or multi-user Linux systems.
  • Reboot after kernel updates when required by the vendor.
  • Track any affected long-term kernel lines still in use.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Compare running kernels with vendor fixed versions or referenced stable commits.
  • Confirm whether shared local user access exists on affected systems.
  • Verify patched kernels are loaded after reboot.
  • Document any systems awaiting vendor guidance or maintenance windows.
Prepared
Confidence
high
Sources
10

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.

cwe · low confidence lookup

CWE-190: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-49727 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
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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.

1CVSS vectors
3Timeline events
1ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2022-49727Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxa32e0eec7042b21ccb52896cf715e3e2641fed93, a32e0eec7042b21ccb52896cf715e3e2641fed93, a32e0eec7042b21ccb52896cf715e3e2641fed93, a32e0eec7042b21ccb52896cf715e3e2641fed93, a32e0eec7042b21ccb52896cf715e3e2641fed93, a32e0eec7042b21ccb52896cf715e3e2641fed93, a32e0eec7042b21ccb52896cf715e3e2641fed93, a32e0eec7042b21ccb52896cf715e3e2641fed93unaffected
LinuxLinux3.5, 0, 4.9.320, 4.14.285, 4.19.249, 5.4.200, 5.10.124, 5.15.49, 5.18.6, 5.19affected
Weakness

CWE details

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

CWE-190 · source CWE mapping

Integer Overflow or Wraparound

Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.