Skip to content
Heist/ feed
Back to feed
UnratedFix available

can: m_can: m_can_{read_fifo,echo_tx_event}(): shift timestamp to full 32 bits

Type: advisorySources: OSV

In the Linux kernel, the following vulnerability has been resolved: can: m_can: m_can_{read_fifo,echo_tx_event}(): shift timestamp to full 32 bits In commit 1be37d3b0414 ("can: m_can: fix periph RX path: use rx-offload to ensure skbs are sent from softirq context") the RX path for peripheral devices was switched to RX-offload. Received CAN frames are pushed to RX-offload together with a timestamp. RX-offload is designed to handle overflows of the timestamp correctly, if 32 bit timestamps are provided. The timestamps of m_can core are only 16 bits wide. So this patch shifts them to full 32 bit before passing them to RX-offload.

Products
Kernel
Affected versions
Not specified
Fixed versions
5.15.54, 5.18.11
CVEs
CVE-2022-49659
Confirmed fixed CVEs
Not specified
Updated in this feed
2 Nov 2026, 18:28 UTC · Revision 1

Source evidence

can: m_can: m_can_{read_fifo,echo_tx_event}(): shift timestamp to full 32 bits

core-osv · Original source

Published 26 Feb 2025, 02:23 UTC

In the Linux kernel, the following vulnerability has been resolved: can: m_can: m_can_{read_fifo,echo_tx_event}(): shift timestamp to full 32 bits In commit 1be37d3b0414 ("can: m_can: fix periph RX path: use rx-offload to ensure skbs are sent from softirq context") the RX path for peripheral devices was switched to RX-offload. Received CAN frames are pushed to RX-offload together with a timestamp. RX-offload is designed to handle overflows of the timestamp correctly, if 32 bit timestamps are provided. The timestamps of m_can core are only 16 bits wide. So this patch shifts them to full 32 bit before passing them to RX-offload.

osv:CVE-2022-49659

Kernel

Fixed versions: 5.15.54, 5.18.11

Complete source record
{
  "id": "b58151419b2a6cf23ed81d060205877c3219ebd9be7ae2694581d40628482335",
  "url": "https://osv.dev/vulnerability/CVE-2022-49659",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "can: m_can: m_can_{read_fifo,echo_tx_event}(): shift timestamp to full 32 bits",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: can: m_can: m_can_{read_fifo,echo_tx_event}(): shift timestamp to full 32 bits In commit 1be37d3b0414 (\"can: m_can: fix periph RX path: use rx-offload to ensure skbs are sent from softirq context\") the RX path for peripheral devices was switched to RX-offload. Received CAN frames are pushed to RX-offload together with a timestamp. RX-offload is designed to handle overflows of the timestamp correctly, if 32 bit timestamps are provided. The timestamps of m_can core are only 16 bits wide. So this patch shifts them to full 32 bit before passing them to RX-offload.",
    "evidence": "osv:CVE-2022-49659",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "5.15.54",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "5.18.11",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2022-49659",
      "aliases": [
        "CVE-2022-49659"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "1be37d3b0414e3db47f6fcba6c16286bbae0cb65"
                },
                {
                  "fixed": "c7333f79888497bfd75dcd02a94eaf836dd1042c"
                },
                {
                  "fixed": "2a2914a5bd7f38efe55a8372178146de82e0bce9"
                },
                {
                  "fixed": "4c3333693f07313f5f0145a922f14a7d3c0f4f21"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49659.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.13.0"
                },
                {
                  "fixed": "5.15.54"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.16.0"
                },
                {
                  "fixed": "5.18.11"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49659.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:22.261772873Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/2a2914a5bd7f38efe55a8372178146de82e0bce9",
        "https://git.kernel.org/stable/c/4c3333693f07313f5f0145a922f14a7d3c0f4f21",
        "https://git.kernel.org/stable/c/c7333f79888497bfd75dcd02a94eaf836dd1042c",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49659.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2022-49659",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49659.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2022-49659",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 488447,
  "published_at": "2025-02-26T02:23:57.411+00:00"
}