SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • ShellShell
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
C

C static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your C code

  • All rules 420
  • Vulnerability14
  • Bug111
  • Security Hotspot19
  • Code Smell276

  • Quick Fix 27
Filtered: 2 rules found
leak
    Impact
      Clean code attribute
        1. Dynamically allocated memory should be released

           Bug
        2. Resources should be closed

           Bug

        Resources should be closed

        intentionality - complete
        reliability
        Bug
        • cwe
        • symbolic-execution
        • leak
        • denial-of-service
        • cert

        A function call to fopen or open must be matched with a call to fclose or close, respectively.

        Why is this an issue?

        How can I fix it?

        More Info

        The standard C library provides fopen and the system call open to open and possibly create files. Each call to one of these functions must be matched with a respective call to fclose or close.

        Failing to close files that have been opened may lead to using up all of the OS’s file handles.

        What is the potential impact?

        If a program does not properly close or release file handles after using them, it will leak resources. In that case, the program will continue to hold onto file handles even when they are no longer needed, eventually exhausting the available file handles.

        If a program has run out of file handles and tries to open yet another file, the file opening operation will fail. This can result in errors or unexpected behavior in the program.

        The program may not be able to read or write to files anymore, which can cause data loss, corruption, or incomplete operations. In some cases, when a program runs out of file handles, it may crash or hang indefinitely. This can happen if the program does not handle the error condition properly or if it enters an infinite loop trying to open files, for instance. In the worst case, a resource leak can lock up everything that runs on the machine.

          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          9.1

        © 2025 SonarSource Sàrl. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use