cve-2024-53223
Vulnerability from cvelistv5
Published
2024-12-27 13:50
Modified
2025-01-20 06:21
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: clk: ralink: mtmips: fix clocks probe order in oldest ralink SoCs Base clocks are the first in being probed and are real dependencies of the rest of fixed, factor and peripheral clocks. For old ralink SoCs RT2880, RT305x and RT3883 'xtal' must be defined first since in any other case, when fixed clocks are probed they are delayed until 'xtal' is probed so the following warning appears: WARNING: CPU: 0 PID: 0 at drivers/clk/ralink/clk-mtmips.c:499 rt3883_bus_recalc_rate+0x98/0x138 Modules linked in: CPU: 0 PID: 0 Comm: swapper Not tainted 6.6.43 #0 Stack : 805e58d0 00000000 00000004 8004f950 00000000 00000004 00000000 00000000 80669c54 80830000 80700000 805ae570 80670068 00000001 80669bf8 00000000 00000000 00000000 805ae570 80669b38 00000020 804db7dc 00000000 00000000 203a6d6d 80669b78 80669e48 70617773 00000000 805ae570 00000000 00000009 00000000 00000001 00000004 00000001 00000000 00000000 83fe43b0 00000000 ... Call Trace: [<800065d0>] show_stack+0x64/0xf4 [<804bca14>] dump_stack_lvl+0x38/0x60 [<800218ac>] __warn+0x94/0xe4 [<8002195c>] warn_slowpath_fmt+0x60/0x94 [<80259ff8>] rt3883_bus_recalc_rate+0x98/0x138 [<80254530>] __clk_register+0x568/0x688 [<80254838>] of_clk_hw_register+0x18/0x2c [<8070b910>] rt2880_clk_of_clk_init_driver+0x18c/0x594 [<8070b628>] of_clk_init+0x1c0/0x23c [<806fc448>] plat_time_init+0x58/0x18c [<806fdaf0>] time_init+0x10/0x6c [<806f9bc4>] start_kernel+0x458/0x67c ---[ end trace 0000000000000000 ]--- When this driver was mainlined we could not find any active users of old ralink SoCs so we cannot perform any real tests for them. Now, one user of a Belkin f9k1109 version 1 device which uses RT3883 SoC appeared and reported some issues in openWRT: - https://github.com/openwrt/openwrt/issues/16054 Thus, define a 'rt2880_xtal_recalc_rate()' just returning the expected frequency 40Mhz and use it along the old ralink SoCs to have a correct boot trace with no warnings and a working clock plan from the beggining.
Impacted products
Vendor Product Version
Linux Linux Version: 6f3b15586eef736831abe6a14f2a6906bc0dc074
Version: 6f3b15586eef736831abe6a14f2a6906bc0dc074
Version: 6f3b15586eef736831abe6a14f2a6906bc0dc074
Version: 6f3b15586eef736831abe6a14f2a6906bc0dc074
Create a notification for this product.
   Linux Linux Version: 6.5
Create a notification for this product.
Show details on NVD website


{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/clk/ralink/clk-mtmips.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "fbb13732c6ffa9d58cedafabcd5ce8fd7ef8ae5a",
              "status": "affected",
              "version": "6f3b15586eef736831abe6a14f2a6906bc0dc074",
              "versionType": "git"
            },
            {
              "lessThan": "fe09d609f2304c7775789090e3f006d786852148",
              "status": "affected",
              "version": "6f3b15586eef736831abe6a14f2a6906bc0dc074",
              "versionType": "git"
            },
            {
              "lessThan": "e29306c0e1ae4b434db32c90705844c77f701be5",
              "status": "affected",
              "version": "6f3b15586eef736831abe6a14f2a6906bc0dc074",
              "versionType": "git"
            },
            {
              "lessThan": "d34db686a3d74bd564bfce2ada15011c556269fc",
              "status": "affected",
              "version": "6f3b15586eef736831abe6a14f2a6906bc0dc074",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/clk/ralink/clk-mtmips.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.5"
            },
            {
              "lessThan": "6.5",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.64",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.11.*",
              "status": "unaffected",
              "version": "6.11.11",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.2",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.13",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nclk: ralink: mtmips: fix clocks probe order in oldest ralink SoCs\n\nBase clocks are the first in being probed and are real dependencies of the\nrest of fixed, factor and peripheral clocks. For old ralink SoCs RT2880,\nRT305x and RT3883 \u0027xtal\u0027 must be defined first since in any other case,\nwhen fixed clocks are probed they are delayed until \u0027xtal\u0027 is probed so the\nfollowing warning appears:\n\n WARNING: CPU: 0 PID: 0 at drivers/clk/ralink/clk-mtmips.c:499 rt3883_bus_recalc_rate+0x98/0x138\n Modules linked in:\n CPU: 0 PID: 0 Comm: swapper Not tainted 6.6.43 #0\n Stack : 805e58d0 00000000 00000004 8004f950 00000000 00000004 00000000 00000000\n 80669c54 80830000 80700000 805ae570 80670068 00000001 80669bf8 00000000\n 00000000 00000000 805ae570 80669b38 00000020 804db7dc 00000000 00000000\n 203a6d6d 80669b78 80669e48 70617773 00000000 805ae570 00000000 00000009\n 00000000 00000001 00000004 00000001 00000000 00000000 83fe43b0 00000000\n ...\n Call Trace:\n [\u003c800065d0\u003e] show_stack+0x64/0xf4\n [\u003c804bca14\u003e] dump_stack_lvl+0x38/0x60\n [\u003c800218ac\u003e] __warn+0x94/0xe4\n [\u003c8002195c\u003e] warn_slowpath_fmt+0x60/0x94\n [\u003c80259ff8\u003e] rt3883_bus_recalc_rate+0x98/0x138\n [\u003c80254530\u003e] __clk_register+0x568/0x688\n [\u003c80254838\u003e] of_clk_hw_register+0x18/0x2c\n [\u003c8070b910\u003e] rt2880_clk_of_clk_init_driver+0x18c/0x594\n [\u003c8070b628\u003e] of_clk_init+0x1c0/0x23c\n [\u003c806fc448\u003e] plat_time_init+0x58/0x18c\n [\u003c806fdaf0\u003e] time_init+0x10/0x6c\n [\u003c806f9bc4\u003e] start_kernel+0x458/0x67c\n\n ---[ end trace 0000000000000000 ]---\n\nWhen this driver was mainlined we could not find any active users of old\nralink SoCs so we cannot perform any real tests for them. Now, one user\nof a Belkin f9k1109 version 1 device which uses RT3883 SoC appeared and\nreported some issues in openWRT:\n- https://github.com/openwrt/openwrt/issues/16054\n\nThus, define a \u0027rt2880_xtal_recalc_rate()\u0027 just returning the expected\nfrequency 40Mhz and use it along the old ralink SoCs to have a correct\nboot trace with no warnings and a working clock plan from the beggining."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-01-20T06:21:33.708Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/fbb13732c6ffa9d58cedafabcd5ce8fd7ef8ae5a"
        },
        {
          "url": "https://git.kernel.org/stable/c/fe09d609f2304c7775789090e3f006d786852148"
        },
        {
          "url": "https://git.kernel.org/stable/c/e29306c0e1ae4b434db32c90705844c77f701be5"
        },
        {
          "url": "https://git.kernel.org/stable/c/d34db686a3d74bd564bfce2ada15011c556269fc"
        }
      ],
      "title": "clk: ralink: mtmips: fix clocks probe order in oldest ralink SoCs",
      "x_generator": {
        "engine": "bippy-5f407fcff5a0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-53223",
    "datePublished": "2024-12-27T13:50:13.371Z",
    "dateReserved": "2024-11-19T17:17:25.024Z",
    "dateUpdated": "2025-01-20T06:21:33.708Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2024-53223\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-12-27T14:15:30.453\",\"lastModified\":\"2024-12-27T14:15:30.453\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nclk: ralink: mtmips: fix clocks probe order in oldest ralink SoCs\\n\\nBase clocks are the first in being probed and are real dependencies of the\\nrest of fixed, factor and peripheral clocks. For old ralink SoCs RT2880,\\nRT305x and RT3883 \u0027xtal\u0027 must be defined first since in any other case,\\nwhen fixed clocks are probed they are delayed until \u0027xtal\u0027 is probed so the\\nfollowing warning appears:\\n\\n WARNING: CPU: 0 PID: 0 at drivers/clk/ralink/clk-mtmips.c:499 rt3883_bus_recalc_rate+0x98/0x138\\n Modules linked in:\\n CPU: 0 PID: 0 Comm: swapper Not tainted 6.6.43 #0\\n Stack : 805e58d0 00000000 00000004 8004f950 00000000 00000004 00000000 00000000\\n 80669c54 80830000 80700000 805ae570 80670068 00000001 80669bf8 00000000\\n 00000000 00000000 805ae570 80669b38 00000020 804db7dc 00000000 00000000\\n 203a6d6d 80669b78 80669e48 70617773 00000000 805ae570 00000000 00000009\\n 00000000 00000001 00000004 00000001 00000000 00000000 83fe43b0 00000000\\n ...\\n Call Trace:\\n [\u003c800065d0\u003e] show_stack+0x64/0xf4\\n [\u003c804bca14\u003e] dump_stack_lvl+0x38/0x60\\n [\u003c800218ac\u003e] __warn+0x94/0xe4\\n [\u003c8002195c\u003e] warn_slowpath_fmt+0x60/0x94\\n [\u003c80259ff8\u003e] rt3883_bus_recalc_rate+0x98/0x138\\n [\u003c80254530\u003e] __clk_register+0x568/0x688\\n [\u003c80254838\u003e] of_clk_hw_register+0x18/0x2c\\n [\u003c8070b910\u003e] rt2880_clk_of_clk_init_driver+0x18c/0x594\\n [\u003c8070b628\u003e] of_clk_init+0x1c0/0x23c\\n [\u003c806fc448\u003e] plat_time_init+0x58/0x18c\\n [\u003c806fdaf0\u003e] time_init+0x10/0x6c\\n [\u003c806f9bc4\u003e] start_kernel+0x458/0x67c\\n\\n ---[ end trace 0000000000000000 ]---\\n\\nWhen this driver was mainlined we could not find any active users of old\\nralink SoCs so we cannot perform any real tests for them. Now, one user\\nof a Belkin f9k1109 version 1 device which uses RT3883 SoC appeared and\\nreported some issues in openWRT:\\n- https://github.com/openwrt/openwrt/issues/16054\\n\\nThus, define a \u0027rt2880_xtal_recalc_rate()\u0027 just returning the expected\\nfrequency 40Mhz and use it along the old ralink SoCs to have a correct\\nboot trace with no warnings and a working clock plan from the beggining.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/d34db686a3d74bd564bfce2ada15011c556269fc\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/e29306c0e1ae4b434db32c90705844c77f701be5\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/fbb13732c6ffa9d58cedafabcd5ce8fd7ef8ae5a\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/fe09d609f2304c7775789090e3f006d786852148\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.